In the last week all of my builds with Google Cloud Registry fail with the following message after 1 minute of build time:
Error response from daemon: No such container: b673590505f0d07c58c5d6413d46d522b4f17549ebe72c523230eff0f8772e6f
Error: No such container: b673590505f0d07c58c5d6413d46d522b4f17549ebe72c523230eff0f8772e6f
seem like the build containers are dying?
Related
I am trying to build and run 8 docker images via docker-compose. Some of them Java Spring projects and some of them angular projects. I am working under corporate proxy. I set proxy settings and docker works correctly. I can build and run images via docker-compose up -d --build command. I can see the logs at first. However after 3-5 minutes, when I tried to run docker ps or docker logs commands I got this error: Error response from daemon: i/o timeout . I tried to find the solution but every question was about the problem occurs during build process which is not my case.
Every time I restart docker, down the services then run the services without problem but after 5 minutes I can not run any docker command. How can I permanently fix this issue. Thanks for any help.
When attempting to pull public images (e.g. python:3.6, node:latest) from Docker, our GitLab runner failed with the following error message:
Running with gitlab-runner 12.2.0 (a987417a)
on GitLab Runner XYZ
Using Docker executor with image python:3.6 ... 00:17
Starting service python:3.6 ...
Pulling docker image python:3.6 ...
ERROR: Preparation failed: Error: No such image: python:3.6 (executor_docker.go:199:0s)
The cause was we exceeded Dockers pull rate limit:
Free plan – anonymous users: 100 pulls per 6 hours
Free plan – authenticated users: 200 pulls per 6
How can I check my current rate?
See https://docs.docker.com/docker-hub/download-rate-limit/#how-can-i-check-my-current-rate
How to increase the rate limit?
Authenticate with Docker Hub to increase to 200 pulls per 6 hours:
docker login
Alternatively you can cache Docker images to reduce the number of calls to DockerHub from your CI/CD infrastructure.
I'm new to Docker so I don't even know where to look. Here are the instructions:
Next, pull a base image that’s compatible with the evaluation build, re-tag it and to a test-run:
docker pull microsoft/windowsservercore:10.0.14393.321
docker tag microsoft/windowsservercore:10.0.14393.321 microsoft/windowsservercore
docker run microsoft/windowsservercore hostname
69c7de26ea48
And this is the error I get on the docker run step:
docker: Error response from daemon: container
6abd92755a8d5d13463eb74f9cc39a798ad0ec898bc1f80ff71205235b63a94f
encountered an error during CreateContainer: failure in a Windows
system call: No hypervisor is present on this system. (0xc0351000)
extra info:
{"SystemType":"Container","Name":"6abd92755a8d5d13463eb74f9cc39a798ad0ec898bc1f80ff71205235b63a94f","Owner":"docker","IsDummy":false,"IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\ProgramData\Docker\windowsfilter\6abd92755a8d5d13463eb74f9cc39a798ad0ec898bc1f80ff71205235b63a94f","Layers":[{"ID":"17e4231d-380e-5dae-b734-0182defea00c","Path":"C:\ProgramData\Docker\windowsfilter\1226fe85e49abd361df8019342eec380ab577268565d2f3d813adcf37d1ccac4"},{"ID":"5fd42877-5043-5d33-a842-d70584cb03eb","Path":"C:\ProgramData\Docker\windowsfilter\53f86340ec419aae07b48e3624d00d7d6f5491f284d8d6e1e62fb7909d9a5fba"}],"HostName":"6abd92755a8d","MappedDirectories":[],"SandboxPath":"C:\ProgramData\Docker\windowsfilter","HvPartition":true,"EndpointList":["91c8a929-c40f-4ad3-a3d2-2906b51cb50a"],"HvRuntime":{"ImagePath":"C:\ProgramData\Docker\windowsfilter\1226fe85e49abd361df8019342eec380ab577268565d2f3d813adcf37d1ccac4\UtilityVM"},"Servicing":false,"AllowUnqualifiedDNSQuery":true}.
I tried to setup Kubernetes executor on Gitlab, but I have this error:
ERROR: Job failed: image pull failed: image pull failed for
someprivateimage:latest,
this may be because there are no credentials on this request. details:
(Error response from daemon: {"message":"Get
https://someprivateimage/latest: denied: access forbidden"})
Anyone have idea why?
You need to either:
Have the docker daemon on your node login to the docker registry. Have a look at the docker login docs
Have the pod definition pull from a private registry. Take a look at these kubernetes docs
If you're going to be doing this often, I recommend the first one.
I had initially thought this was the same as: Kubernetes imagePullSecrets not working; getting "image not found"
However, even disabling authentication (to avoid the need for secrets) still produces the same error.
So, Kubernetes trying to pull images from Nexus Docker registry keeps producing the kubernetes error:
"Failed to pull image "nexus.mydomain.co.uk/nginx": Error: image nginx:latest not found"
This is also reflected in the Nexus logs:
2016-06-22 14:51:26,929+0000 WARN [qtp556619582-227] docker org.sonatype.nexus.repository.docker.internal.V1Handlers - Error: GET /v1/repositories/nginx/images: 404 - org.sonatype.nexus.repository.docker.internal.V1Exception$ImagesNotFound: images not found
I can't get onto the kube boxes to try a pull, however, when I run "docker pull" from my mac command line all is well and good.