I'm using docker desktop ,when I'm trying to pull image it bumps into following error:
Error response from daemon: received unexpected HTTP status: 500
Server Error
where I'm wrong?
Issue disappeared when I uninstalled Docker desktop and installed docker desktop edge.
Related
during OpenShift installation from a local mirror registry, after I started the bootstrap machine i see the following error in the journal log:
release-image-download.sh[1270]:
Error: error pulling image "quay.io/openshift-release-dev/ocp-release#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129":
unable to pull quay.io/openshift-release-dev/ocp-release#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129: unable to pull image:
Error initializing source docker://quay.io/openshift-release-dev/ocp-release#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129:
(Mirrors also failed: [my registry:5000/ocp4/openshift4#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129: Error reading manifest
sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129 in my registry:5000/ocp4/openshift4: manifest unknown: manifest unknown]):
quay.io/openshift-release-dev/ocp-release#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129: error pinging docker registry quay.io:
Get "https://quay.io/v2/": dial tcp 50.16.140.223:443: i/o timeout
Does anyone have any idea what it can be?
The answer is here in the error:
... dial tcp 50.16.140.223:443: i/o timeout
Try this on the command line:
$ podman pull quay.io/openshift-release-dev/ocp-release#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129
You'll need to be authenticated to actually download the content (this is what the pull secret does). However, if you can't get the "unauthenticated" error then this would more solidly point to some network configuration.
That IP resolves to a quay host (you can verify that with "curl -k https://50.16.140.223"). Perhaps you have an internet filter or firewall in place that's blocking egress?
Resolutions:
fix your network issue, if you have one
look at doing an disconnected /airgap install -- https://docs.openshift.com/container-platform/4.7/installing/installing-mirroring-installation-images.html has more details on that
(If you're already doing an airgap install and it's your local mirror that's failing, then your local mirror is failing)
I have installed Docker using Docker Toolbox as I am using Windows 10 Home version. But when I connect to Docker in Intellij its throwing below error.
Status 400: Client sent an HTTP request to an HTTPS server.
How to resolve this?
Error
Docker Configuration
Try changing the Engine API URL from tcp://$HOST:$PORT to https://$HOST:$PORT.
I have good experience in docker. But new in using docker repository with Artifactory.
Currently I am facing this error when I try to login:
Error response from daemon: login attempt to https://dev.artifactory.com/v2/ failed with status: 404 Not Found
Not sure what is missing. I have also installed nginx with the help of docker documentation. Still it does not work.
When I used to login with command "docker login dev.artifactory.com:80" it gives the error Error response from daemon: Get https://dev.artifactory.com:80/v2/: net/http: TLS handshake timeout
Can someone help me on this.
Thanks
I made a registry exactly how it says in the docker documentation and for some reason whenever I try pushing an image to it, it throws a 404 error at me.
here is the error
Error: Status 404 trying to push repository stelasite: "404 page not found\n"
and on the server side, this
11/8/2015 6:33:00 PM173.12.71.226 - - [08/Nov/2015:23:33:00 +0000] "GET /v2/ HTTP/1.1" 401 87 "" "docker/1.8.2-fc22 go/go1.5.1 kernel/4.2.3-200.fc22.x86_64 os/linux arch/amd64"
11/8/2015 6:33:05 PM173.12.71.226 - - [08/Nov/2015:23:33:05 +0000] "PUT /v1/repositories/stelasite/ HTTP/1.1" 404 19 "" "docker/1.8.2-fc22 go/go1.5.1 kernel/4.2.3-200.fc22.x86_64 os/linux arch/amd64"
Does anyone have any idea what's going on? Apparently it can't connect to the v1 api but I don't know why the docker cli would even try that.
I had the same issue, and solved it by getting my local docker environment in order.
The cause of my issue was either that my Docker client was too old, or that I had a mismatch in docker version between my Docker client (1.7.1) and docker-machine VM (1.8.1). I had a version mismatch because I created the VM and then downgraded my docker client. The access logs on the registry said the client was 1.8.1 even though my host system had 1.7.1. I deleted the docker-machine VM (docker-machine rm <environment name>), then uninstalled docker and re-installed 1.10.0 via Homebrew.
If you're running multiple Docker registries behind a load balancer, another thing that might cause problems with pushing is a mismatch in HTTP secrets. You'd need to explicitly set them all to the same thing using either the environment variable REGISTRY_HTTP_SECRET or like this in the config file:
http:
secret: mysecret
I saw a blog post from 2013 that claimed the secret needs to be 64 characters long, but I don't see that in the docs
I had the same error when the registry machine was responding very slow. In my case it was a issue with one of the dns servers.
Changing the dns server, made push work again. You can test it by pinging the distribution server and see if it's very slow to respond or resolve the hostname.
If you run docker with --debug, this is the output from logs:
DEBU[0013] Calling POST /images/{name:.*}/push
INFO[0013] POST /v1.20/images/docker-distribution.company.net:5000/nginx/push?tag=
DEBU[0023] hostDir: /etc/docker/certs.d/docker-distribution.company.net:5000
DEBU[0033] Trying to push docker-distribution.company.net:5000/nginx to https://docker-distribution.company.net:5000 v2
DEBU[0038] Error getting v2 registry: Get https://docker-distribution.company.net:5000/v2/: net/http: request canceled while waiting for connection
DEBU[0038] Trying to push docker-distribution.company.net:5000/nginx to https://docker-distribution.company.net:5000 v1
DEBU[0038] hostDir: /etc/docker/certs.d/docker-distribution.company.net:5000
DEBU[0038] attempting v2 ping for registry endpoint https://docker-distribution.company.net:5000/v2/
DEBU[0043] Endpoint https://docker-distribution.company.net:5000/v2/ is eligible for private registry. Enabling decorator.
You can see that the error is "request canceled while waiting for connection".
I'm recently update to docker version 1.8.2, build 0a8c2e3 but when I execute any docker pull , the output show 403 error trying to download image layers.
Output:
docker pull cassandra [80/221]
Using default tag: latest
Pulling repository docker.io/library/cassandra
f86e3cc71c14: Error pulling image (latest) from docker.io/library/cassandra, Server error: Status 403 while fetching image layer (756acc691e31cf79b1a74a404f91b
2f4365cba936cec3f6eb4bc94ef419b33da) 404f91b2f4365cba936cec3f6eb4bc94ef419b33da)
8c00acfb0175: Download complete
756acc691e31: Error pulling dependent layers
Error pulling image (latest) from docker.io/library/cassandra, Server error: Status 403 while fetching image layer (756acc691e31cf79b1a74a404f91b2f4365cba936ce
c3f6eb4bc94ef419b33da)
I got the same problem because the new docker registry on Docker Hub seems to use an external service on cloudfront.net and this site forbids access from my country. The full error was:
Error statting layer: Head https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?Expires=1443470694&Signature=U11dGhTtNemJC-r1jR7fVmd5nlEq~imRzqgQKAmhmmxWLpLnN0Eb7iprdGvbD49Bc65j7omMZQG5cZnO6B3kcvMGF96z0pKJ8rHYJSZZgg4Wv6YoLfuvH~Wr2Sa11vW3ZvfssoK0NfVTsTFvq801TEAQ0g74gN8A6IrsZ8x0RH8_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: net/http: TLS handshake timeout
I found this running the docker daemon with -D (debug) and reading the log at /var/log/upstart/docker.log. Also, if you're behind a proxy, verify that your proxy isn't denying access.