Good day!
I have a little problem with pushing my image to docker hub. First of my software versions:
vagrant#debian-8-docker:~$ docker version
Client version: 0.11.1
Client API version: 1.11
Go version (client): go1.2.1
Git commit (client): fb99f99
Server version: 0.11.1
Server API version: 1.11
Git commit (server): fb99f99
Go version (server): go1.2.1
vagrant#debian-8-docker:~$
vagrant#debian-8-docker:~$ cat /etc/*release
PRETTY_NAME="Debian GNU/Linux jessie/sid"
NAME="Debian GNU/Linux"
ID=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support/"
BUG_REPORT_URL="http://bugs.debian.org/"
vagrant#debian-8-docker:~$ uname -a
Linux debian-8-docker 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64 GNU/Linux
vagrant#debian-8-docker:~$
So, first I pull ubuntu image:
$ docker pull ubuntu:12.04
It rans ok, so I create container and installed ping utility:
$ docker run -i ubuntu:12.04 apt-get install -y inetutils-ping
After that I commit the changes:
$ docker commit -m 'Installed ping utility to ubuntu' -a 'Vasiliy Ozerov' 9a817769bd9a vozerov/ubuntu-ping:v1
And tried to push:
$ docker push vozerov/ubuntu-ping
The push refers to a repository [vozerov/ubuntu-ping] (len: 1)
Sending image list
Pushing repository vozerov/ubuntu-ping (1 tags)
511136ea3c5a: Image already pushed, skipping
663644853bf8: Pushing
2014/06/13 19:07:16 HTTP code 400 while uploading metadata: {"error": "Image depends on an unauthorized parent"}
docker login was executed successfully:
$ docker login
Username (vozerov):
Login Succeeded
So I really don't understand what is this.
Please, can you help me? Thanks.
Docker System Status and mail thread suggest this is not your fault, but I do not know really.
Related
wget not works in centOS 5.11.
Do you have any idea?
sh-3.2# head -n 1 /etc/issue
CentOS release 5.11 (Final)
sh-3.2# wget https://www.cpan.org/src/5.0/perl-5.36.0.tar.gz
--2022-10-21 04:19:21-- https://www.cpan.org/src/5.0/perl-5.36.0.tar.gz
Resolving www.cpan.org... 151.101.53.55, 2a04:4e42:d::311
Connecting to www.cpan.org|151.101.53.55|:443... connected.
OpenSSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Unable to establish SSL connection.
I pushed the image to docker hub.
You can run it by
docker run -it zhongpengqun/centos5.11 /bin/sh
My system:
georgek#kalamata:~/dev/docker/flights$ uname -a
Linux kalamata 5.15.0-33-generic #34-Ubuntu SMP Wed May 18 13:34:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
georgek#kalamata:~/dev/docker/flights$ minikube version
minikube version: v1.25.2
commit: 362d5fdc0a3dbee389b3d3f1034e8023e72bd3a7
georgek#kalamata:~/dev/docker/flights$ kubectl version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.24.0
Kustomize Version: v4.5.4
Server Version: v1.23.3
I have a toy private registry created inside an AWS VM.
I start minikube with
minikube start --insecure-registry <IP>:5000
I try to do a deployment with
kubectl create deployment flights-node --image=<IP>:5000/flights
... and it fails with
Failed to pull image "<IP>:5000/flights": rpc error: code = Unknown desc = Error response from daemon: Get "http://<IP>:5000/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
I did do a minikube ssh and tried to run a docker pull <IP>:5000/flights with no success so I know what the problem is (the same docker pull command from my own docker install outside minikube works fine!).
I am new to kubernetes so any suggestions/ideas will help me immensely!
I was looking at similar posts made on private registries and minikube and all had a simple underlying premise, reboot :).
I did reboot my system and voila I am now able to fetch the image from my private registry.
If anyone knows the underlying reason as to why a reboot is needed please share.
CentOS 7
Docker 20.10.5
java version "1.8.0_162"
PostgreSQL 9.6.2
I try to start SonarQube 7.6.9 in Docker like this:
sudo docker run --name sonarqube -p 9000:9000 --add-host host.docker.internal:host-gateway -e SONARQUBE_JDBC_USERNAME=sonar -e SONARQUBE_JDBC_PASSWORD=sonar -e SONARQUBE_JDBC_URL=jdbc:postgresql://host.docker.internal:5432/sonar sonarqube:7.6.9
But I get error:
ERROR web[][o.s.s.p.PlatformImpl] Web server startup failed: Current version is too old. Please upgrade to Long Term Support version firstly.
P.S.
If I start without connect to PostgreSQL then SonarQube 7.6.9 is success run
sudo docker run --name sonarqube -p 9000:9000 sonarqube:7.6.9
I was getting this error when trying to upgrade from Sonar 6.7.5 to Sonar 8.9.2
Searching in the web i found that this happens because migration route is needed between versions.
In my case it was not possible to jump directly from version 6.7.5 to version 8.9.2. First I had to jump to version 7.9.6 and then to version 8.9.2 (
you can read more about Migration path in: https://docs.sonarqube.org/latest/setup/before-you-upgrade/).
I hope this can serve you.
I'm new to docker and I'm trying to run a postgres database docker with the following command :
docker run --name rva-db -e POSTGRES_PASSWORD=rva -e POSTGRES_DB=rva-db -d postgres -p 5432:5432
If I'm trying to run it without the -p option, it seems to work fine, but I can't reach it from my local pg-admin, I thought I need to add the port link to reach it.
Anyway, the container always crash after few seconds and when i'm trying to start it with the start command I'm getting the following return :
docker start -a rva-db
FATAL: invalid value for parameter "port": "5432:5432"
What did I miss ?
FYI, I'm running it on a MacOS with the following docker version :
$ docker version
Client:
Version: 1.12.1
API version: 1.24
Go version: go1.7.1
Git commit: 6f9534c
Built: Thu Sep 8 10:31:18 2016
OS/Arch: darwin/amd64
Server:
Version: 1.12.1
API version: 1.24
Go version: go1.6.3
Git commit: 23cf638
Built: Thu Aug 18 17:52:38 2016
OS/Arch: linux/amd64
Run the container typing -p option before the image name
docker run --name rva-db -e POSTGRES_PASSWORD=rva -e POSTGRES_DB=rva-db -d -p 5432:5432 postgres
As for Docker run reference docker run has this format
docker run [OPTIONS] IMAGE[:TAG|#DIGEST] [COMMAND] [ARG...]
Options must be before image name. After that you can set entrypoint or command (when theyy differ from default from Dockerfile) and their arguments.
I have the following line in my Dockerfile:
RUN git clone https://github.com/assafg/youtube-remote.git ./youtube-remote
When executing sudo docker build -t 'yremote' .
I get the following error:
Cloning into './youtube-remote'... fatal: unable to access
'https://github.com/assafg/youtube-remote.git/': Could not resolve
host: github.com The command '/bin/sh -c git clone
https://github.com/assafg/youtube-remote.git ./youtube-remote'
returned a non-zero code: 128
Running clone command from command line works fine.
This can happen if your container can't connect to the internet. Possibly because it was started with a weird networking option? Run this command to check default internet connectivity:
docker run ubuntu apt install -y git && \
git clone https://github.com/assafg/youtube-remote.git ./youtube-remote
If that container successfully pulls down the repo, it probably means the first container has a networking problem. Try to restart, or change networking settings.
Docker Network just became a first class citizen in the Docker ecosystem. It's a really fast-moving project. This advice applies to v1.8
This is not a very scientific answer but sometimes docker restart helps especially in cases connected with docker network.