Error: image orgsync/java8 not found - docker

I'm new to Docker and just cloned this repo:
https://hub.docker.com/r/clifton/ib-gateway/
I then ran the build on dockerhub, and got this error:
Starting to clone
Cloning into '.'...
Cloning done
Starting Build
KernelVersion: 3.13.0-40-generic
Os: linux
BuildTime: 2016-02-22T21:37:01.910365059+00:00
ApiVersion: 1.22
Version: 1.10.2
GitCommit: c3959b1
Arch: amd64
GoVersion: go1.5.3
Starting build of index.docker.io/vgoklani/docker-ib-gateway:latest...
Step 1 : FROM orgsync/java8
Error: image orgsync/java8 not found
https://hub.docker.com/r/vgoklani/docker-ib-gateway/builds/bbaiqpyxasq6lg3sd6nzgp5/
Any ideas on what's happening?

The error is clear, the orgsync/java8 image does not exist. It may have been deleted. Causing build fail.
You can replace it by the official java image by replacing orgsync/java8 by java in the dockerfile

Related

Bitbucket pipeline - error installing pre-commit ts-lint

I have a step in my pipeline that runs our configured pre-commit on Bitbucket:
...
- step:
name: Passing linters
image: python:3.7-slim-stretch
script:
- pip3 install "pre-commit==2.17.0"
- apt-get update && apt-get --assume-yes install git
- pre-commit run --all-files
No changes were made but it suddenly stopped working.
The pipeline result:
+ pre-commit run --all-files
[INFO] Initializing environment for https://github.com/psf/black.
[INFO] Initializing environment for https://github.com/psf/black:click==8.0.4.
[INFO] Initializing environment for https://github.com/pre-commit/pre-commit-hooks.
[INFO] Initializing environment for https://github.com/maximevast/pre-commit-tslint/.
[INFO] Initializing environment for https://github.com/maximevast/pre-commit-tslint/:tslint-react#4.1.0,tslint#5.20.1,typescript#4.0.2.
[INFO] Installing environment for https://github.com/psf/black.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for https://github.com/pre-commit/pre-commit-hooks.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for https://github.com/maximevast/pre-commit-tslint/.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
An unexpected error has occurred: CalledProcessError: command: ('/root/.cache/pre-commit/repo1234/node_env-default/bin/node', '/root/.cache/pre-commit/repo1234/node_env-default/bin/npm', 'install', '--dev', '--prod', '--ignore-prepublish', '--no-progress', '--no-save')
return code: 1
expected return code: 0
stdout: (none)
stderr:
/root/.cache/pre-commit/repo1234/node_env-default/bin/node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /root/.cache/pre-commit/repo1234/node_env-default/bin/node)
/root/.cache/pre-commit/repo1234/node_env-default/bin/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /root/.cache/pre-commit/repo1234/node_env-default/bin/node)
/root/.cache/pre-commit/repo1234/node_env-default/bin/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /root/.cache/pre-commit/repo1234/node_env-default/bin/node)
Check the log at /root/.cache/pre-commit/pre-commit.log
pre-commit utilizes nodeenv to bootstrap node environments
it does this by downloading a copy of node and provisioning an environment (when node is not available). a few days ago node 18.x was released and the prebuilt binaries require a relatively-recent version of glibc
there's a few ways you can work around this:
1. select a specific version of node using language_version / default_language_version
# using default_language_version
default_language_version:
node: 16.14.2
# on the hook itself
repos:
- repo: https://github.com/maximevast/pre-commit-tslint
rev: ...
hooks:
- id: tslint
language_version: 16.14.2
2. use a newer base image
stretch is a bit old, perhaps try instead 3.7-slim-buster instead ?
this will get you a more modern version of glibc
image: python:3.7-slim-buster
3. install node into your image
this will skip the "download node" step of pre-commit by default (specifically it'll default to language_version: system when a suitable node is detected)
this will vary based on your image setup
disclaimer: I created pre-commit

Gradle with Java11 build produces intermittent compilation errors

We are using gradle:6.9.1-jdk11-hotspot image to build one of our java jar components.
Gradle 6.9.1
Build time: 2021-08-20 11:15:18 UTC.
Revision: f0ddb54aaae0e44f0a7209c3c0274d506ea742a0
Kotlin: 1.4.20
Groovy: 2.5.12
Ant: Apache Ant(TM) version 1.10.9 compiled on September 27 2020
JVM: 11.0.11 (AdoptOpenJDK 11.0.11+9)
OS: Linux 5.10.47-linuxkit amd64.
The Gradle build file also use io.freefair.aspectj.compile-time-weaving:3.8.4 for compile time weaving.
We get the following compilation errors
The type javax.xml.stream.XMLEventReader is not accessible.
import javax.xml.stream.XMLEventReader;
The type javax.xml.stream.XMLInputFactory is not accessible
import javax.xml.stream.XMLInputFactory;
XMLEventReader cannot be resolved to a type
private XMLEventReader xmlEventReader;
XMLInputFactory cannot be resolved
XMLInputFactory xmlInputFactory = XMLInputFactory.newInstance();
This compilation error does not happen consistently and it happens intermittently. Retrying after a couple of times the build succeeds.
We use docker-compose of version 2.0.1 to build the image. The Gradle build is executed as part of building the docker image.
Here is the Dockerfile:
FROM gradle:6.9.1-jdk11-hotspot
ENV GRADLE_USER_HOME=/app/.gradle
USER root
WORKDIR app/libs
COPY common/*.gradle ./common/
COPY common/src ./common/src
RUN gradle --stacktrace --no-daemon :common:build

Helm is stuck - status: pending-install

I'm trying to deploy one of my service, but I'm getting the error:
##[error]Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress
What I have is:
development#Azure:~$ helm version
version.BuildInfo{Version:"v3.4.0", GitCommit:"7090a89efc8a18f3d8178bf47d2462450349a004", GitTreeState:"clean", GoVersion:"go1.14.10"}
development#Azure:~$ helm list -Aa
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
azuredevops novadevspace 1 2021-04-17 20:32:01.929625514 +0000 UTC pending-install sampleapp-v0.2.0
development#Azure:~$ helm install azuredevops . --debug
install.go:172: [debug] Original chart version: ""
install.go:189: [debug] CHART PATH: /home/development
walk.go:74: found symbolic link in path: /home/development/clouddrive resolves to /usr/csuser/clouddrive
Killed
development#Azure:~$
development#Azure:~$ helm list -Aa
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
azuredevops novadevspace 1 2021-04-17 20:32:01.929625514 +0000 UTC pending-install sampleapp-v0.2.0
development#Azure:~$
For some reason, the process status is "pending-install", and I'm not able to kill it.
Someone can help me to delete it in order to do a new deployment?
Please try helm rollback and then helm delete releasename

Travis-CI - chrome 62 instead of 77

For two days Travis CI returns version 62 of chrome instead of 77, do you also have the problem on your CI / CD?
.travis.yml (source)
addons:
chrome: stable
trace: (source)
$ export CHROME_SOURCE_URL=https://dl.google.com/dl/linux/direct/google-chrome-stable_current_amd64.deb
Installing Google Chrome stable
1.17s$ wget --no-verbose -O /tmp/$(basename $CHROME_SOURCE_URL) $CHROME_SOURCE_URL
2019-09-11 15:41:31 URL:https://dl.google.com/dl/linux/direct/google-chrome-stable_current_amd64.deb [62302944/62302944] -> "/tmp/google-chrome-stable_current_amd64.deb" [1]
dpkg-deb: error: archive '/tmp/google-chrome-stable_current_amd64.deb' has premature member 'control.tar.xz' before 'control.tar.gz', giving up
dpkg: error processing archive /tmp/google-chrome-stable_current_amd64.deb (--install):
subprocess dpkg-deb --control returned error exit status 2
Errors were encountered while processing:
/tmp/google-chrome-stable_current_amd64.deb
Google Chrome 62.0.3202.94
I add install dpkg
.travis.yml:
addons:
apt:
packages:
- dpkg
chrome: stable
It's a known bug with the dpkg package not supporting xz compressed packages and latest versions of Chrome apparently use it.
The best solution would be to upgrade to dist: xenial build env since trusty are quire old now. Or update the package I guess.
See https://github.com/travis-ci/travis-ci/issues/9361
Changing the Linux distribution fixed the issue for me.
Change:
dust: trusty
To:
dist: xenial
In the .travis.yml file, change my Chrome version from 62.0.3202.94 to 81.0.4044.138
I fixed it on our opensource project by forcing dpkg reinstall:
https://github.com/PrestaShop/PrestaShop/pull/15581

Tensorflow Hub Build from Source Failing

I'm having a problem with Building TF Hub from Source. Can Anyone please help me out? I've been following the steps as given in https://github.com/tensorflow/hub/blob/master/tensorflow_hub/pip_package/PIP.md
I've installed bazel 0.24.1.
Error I'm Getting:
ERROR: /home/tf_hub/hub/WORKSPACE:17:1: name 'git_repository' is not defined
ERROR: /home/tf_hub/hub/WORKSPACE:40:1: name 'http_archive' is not defined
ERROR: /home/tf_hub/hub/WORKSPACE:47:1: name 'new_http_archive' is not defined
ERROR: Error evaluating WORKSPACE file
ERROR: error loading package '': Encountered error while reading extension file 'tools/build_defs/repo/http.bzl': no such package '#bazel_tools//tools/build_defs/repo': error loading package 'external': Could not load //external package
ERROR: error loading package '': Encountered error while reading extension file 'tools/build_defs/repo/http.bzl': no such package '#bazel_tools//tools/build_defs/repo': error loading package 'external': Could not load //external package
INFO: Elapsed time: 2.552s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
Bazel Version: 0.24.1
Python Version: 3
Tensorflow Version: 2.0.0a
Commands to Reproduce:
(env)~/tf_hub$ git clone https://github.com/tensorflow/hub
(env)~/tf_hub$ cd hub && bazel build tensorflow_hub/pip_package:build_pip_package
Expected Output: No Error. Build Sucessful
Latest Versions of Bazel Doesn't support git_repository (which is still used by tensorflow_hub), so Uninstalling Bazel 0.24.1 and installing Bazel 0.18.1 worked.

Resources