has anyone seen that? I'm running a local registry, image uploaded from other machine, can be accessed on yet another machine but not locally where the registry is installed.
Docker version 1.5.0, build a8a31ef/1.5.0
2.6.32-504.8.1.el6.x86_64
[root#hhh radek]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fb50aaacd282 registry:2.0 "registry cmd/regist 15 minutes ago Up 15 minutes 0.0.0.0:8180->5000/tcp high_torvalds
[root#hhh radek]# docker pull hhh:8180/name/oracle:latest
...
75550c09ec78: Pulling fs layer
3912e3898de8: Pulling fs layer
7d513a058ccf: Layer already being pulled by another client. Waiting.
7d513a058ccf: Download complete
FATA[0000] Error: image name/oracle:latest not found
Related
I am pulling image from my local docker registry provider by nexus 3 in kubernetes cluster, but throw this error:
Failed to pull image "192.168.31.2:8080/goharbor/harbor-portal:v2.0.1": rpc error: code = Unknown desc = error pulling image configuration: unknown blob
when I execute this command using docker in k8sslave3 host machine:
[root#k8sslave3 ~]# sudo docker pull 192.168.31.2:8080/goharbor/harbor-portal:v2.0.1
v2.0.1: Pulling from goharbor/harbor-portal
a10779388d4e: Pulling fs layer
b3655b0b1b25: Pulling fs layer
0c2039460571: Pulling fs layer
7ea51f62bc90: Waiting
9b7d884050ac: Waiting
191f5a91ea62: Waiting
a0935490d8f5: Waiting
dd7dc6b4b30d: Waiting
502017fcbb22: Waiting
error pulling image configuration: unknown blob
I am read the question and tell me the docker image does not exists. But when I execute pull in 192.168.31.2, the output like this:
[dolphin#localhost docker]$ sudo docker pull 192.168.31.2:8080/goharbor/harbor-portal:v2.0.1
[sudo] password for dolphin:
v2.0.1: Pulling from goharbor/harbor-portal
Digest: sha256:d40f87352700cde0f91b9f758b3e47c9ebfe4358f73fa26a6675415b3fbc6b96
Status: Image is up to date for 192.168.31.2:8080/goharbor/harbor-portal:v2.0.1
192.168.31.2:8080/goharbor/harbor-portal:v2.0.1
so now I am confusing, what should I do to fix this problem? this is the docker image in nexus repository:
I am read the question and tell me the docker image does not exists.
But when I execute pull in 192.168.31.2, the output like this:
[dolphin#localhost docker]$ sudo docker pull 192.168.31.2:8080/goharbor/harbor-portal:v2.0.1
[sudo] password for dolphin:
v2.0.1: Pulling from goharbor/harbor-portal
Digest: sha256:d40f87352700cde0f91b9f758b3e47c9ebfe4358f73fa26a6675415b3fbc6b96
Status: Image is up to date for 192.168.31.2:8080/goharbor/harbor-portal:v2.0.1
192.168.31.2:8080/goharbor/harbor-portal:v2.0.1
That is rather expected that it works if you pull the image from the host that hosts the registry.
As you created the tag from that host, the Docker client doesn't need to pull anything from the private registry, it returns directly the image from the local Docker registry of the host.
Look at the message :
Status: Image is up to date for
192.168.31.2:8080/goharbor/harbor-portal:v2.0.1
Your image configuration/data is very probably corrupted in the registry.
Try to reupload it and check also that its size is not too big (several GBs may be too much sometimes) because it may create some troubles in registry uploading/storing.
$ docker pull oraclelinux
Using default tag: latest
latest: Pulling from library/oraclelinux
c93adbd5ca8c: Downloading [==================================================>] 85.96MB/85.96MB
unexpected EOF
$ docker --version
Docker version 18.09.2, build 6247962
I notice that docker pull continously retries with back-off for a few times and eventually fails with unexpected EOF. Same issue observed if pulling centos, debian image.
The docker pull of this image from a repository in local network succeeds. I'm trying to figure out the failure for pulls from github.io.
docker pull for smaller size images (ex: alpine, helloworld) succeeds.
Running Docker Desktop Version 2.0.0.3 (31259) on MacOS High Sierra. Restarting Docker did not resolve the issue.
Any pointers are greatly appreciated.
Found an answer. I had to use Manual Proxy Configuration within Docker Desktop to point to an internal corp proxy for this to work.
So I create a Docker hub image as follows, worked fine
Created new empty repository in DockerHub
Uploaded my DockerFile to my webserver
ssh *qnapserver*
docker build *DockerFileUrl*
docker login *DockerHubUsername* *DockerHubPassword*
docker images (to get imageId of built image)
docker tag *imageId* *DockerHubNameSpace*/*DockerHubRepository*:latest
docker push *DockerHubNameSpace*/*DockerHubRepository*:latest
A few weeks later I need to rebuild image for new software version, so I did
ssh *qnapserver*
docker build *DockerFileUrl*
docker login *DockerHubUsername* *DockerHubPassword*
docker images (to get imageId of built image)
docker tag *imageId* *DockerHubNameSpace*/*DockerHubRepository*:latest
docker push *DockerHubNameSpace*/*DockerHubRepository*:latest
but the final push command fails with
The push refers to a repository [docker.io/songkong/songkong-arm32]
d68f3fa1b903: Preparing
a0fcc8fd26d0: Preparing
e921eb3da019: Preparing
30b60a45df09: Preparing
8a9717d91a27: Preparing
fcf19287cca0: Waiting
72b719a20b26: Waiting
denied: requested access to the resource is denied
Running docker images gives:
[~] # docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
songkong/songkong-arm32 latest d2ab52ce970a 14 minutes ago 179MB
arm32v6/openjdk 8-jre-alpine d6163b61a7aa 8 days ago 72.9MB
songkong/songkong-arm32 <none> a57032901b5c 2 weeks ago 169MB
songkong/songkong-arm32 <none> 8f3ae4b75feb 2 weeks ago 162MB
The issue seems to be that I wasnt logged onto DockerHub properly
docker login *DockerHubUsername* *DockerHubPassword*
did not return an error, but I tried doing
docker login
and entering username and password at the prompt and then the push worked ok.
Are you using Docker for Mac ?
There is a bug with the docker login CLI command.
Please see this github issue and add your experience if you can :
https://github.com/docker/for-mac/issues/2016
On launching app using docker getting message ERROR: unknown blob as per
docker-compose -f /usr/local/tmp/khufu01/loud_deploy/nokube/dind/docker-compose.yml up -d
Pulling myimage(localhost:5000/forelsket/myimage:latest)...
latest: Pulling from forelsket/myimage
50aff78429b1: Pulling fs layer
f6d82e297bce: Pulling fs layer
fdd34fec4c74: Pulling fs layer
151b5e27e3b4: Pulling fs layer
d477e9b677eb: Pulling fs layer
7e8156598779: Download complete
ca2064fc9543: Download complete
ERROR: unknown blob
after adding flag --verbose to my docker-compose call it now shows
docker-compose --verbose -f /usr/local/tmp/khufu01/loud_deploy/nokube/dind/docker-compose.yml up -d
Pulling myimage(localhost:5000/forelsket/myimage:latest)...
latest: Pulling from forelsket/myimage
50aff78429b1: Pulling fs layer
f6d82e297bce: Pulling fs layer
fdd34fec4c74: Pulling fs layer
151b5e27e3b4: Pulling fs layer
d477e9b677eb: Pulling fs layer
7e8156598779: Download complete
ca2064fc9543: Download complete
ERROR: compose.cli.main.main: unknown blob
this is on linux using latest docker
docker 18.02.0-ce-rc2
Kernel Version: 4.4.0-112-generic
Operating System: Ubuntu 16.04.3 LTS
OSType: linux
Architecture: x86_64
seems strange as this app ran fine this morning ... I am using a local docker repository of registry:2 at localhost:5000
Solution ERROR: unknown blob is trying to say one or more layers of the image is not found
... this makes sense since earlier today all local docker images were deleted
So after building the missing image the docker-compose up ran fine
Goes without saying this error can be avoided if a preliminary step first determines whether the image even exists in chosen image repository
In my case removing /var/lib/docker made things worse - pulling failed with
$ docker-compose up -d
Pulling mysql-service (mysql:5.7.17)...
5.7.17: Pulling from library/mysql
6d827a3ef358: Pulling fs layer
ed0929eb7dfe: Pulling fs layer
03f348dc3b9d: Pulling fs layer
fd337761ca76: Waiting
7e6cc16d464a: Waiting
ca3d380bc018: Waiting
3fe11378d5c0: Waiting
2b5dfd325645: Waiting
b54281d17fbe: Waiting
7eae4db8eea5: Waiting
76cf68e17b09: Waiting
ERROR: open /var/lib/docker/tmp/GetImageBlob310458906: no such file or directory
Purging docker solved the problem.
i have installed docker on ubuntu14.04-64bit,when i want to run a demo,error occurs,
y7:~$ docker run docker/whalesay cowsay boo
Unable to find image 'docker/whalesay:latest' locally
Repository docker/whalesay already being pulled by another client. Waiting.
Error response from daemon: No such image: docker/whalesay (tag: latest)
7:~$ docker run docker/whalesay
Unable to find image 'docker/whalesay:latest' locally
latest: Pulling from docker/whalesay
e9e06b06e14c: Pulling fs layer
a82efea989f9: Pulling fs layer
e9e06b06e14c: Error pulling dependent layers
07f8e8c5e660: Pulling fs layer
676c4a1897e6: Pulling fs layer
5b74edbcaa5b: Pulling fs layer
1722f41ddcb5: Pulling fs layer
99da72cfe067: Pulling fs layer
5d5bd9951e26: Pulling fs layer
fb434121fc77: Download complete
fb434121fc77: Pulling image (latest) from docker/whalesay, endpoint: https://regfb434121fc77: Error pulling image (latest) from docker/whalesay, endpoint: https://registry-1.docker.io/v1/, Server error: Status 0 whilefetching image layer (fb434121fc77: Error pulling image (latest) from docker/whalesay, Server error: Status 0 while fetching image layer (e9e06b06e14c2f7d8df0251e3bb852c3a10a70639498Error pulling image (latest) from docker/whalesay, Server error: Status 0 while fetching image layer (e9e06b06e14c2f7d8df0251e3bb852c3a10a70639498163d4f180a823c18fdfc)
The message Error response from daemon: No such image: docker/whalesay (tag: latest) is a little confusing, but the real error is the line just above it:
Repository docker/whalesay already being pulled by another client. Waiting.
If you begin pulling a repo and then controlc, the Docker daemon will hang out for a while and refuse to do further pulls on that repo.
Sometimes a system might require to have both a few local docker repos, as well as having docker images hosted on DockerHub. The best way to be assured that you are pointing the the DockerHub repo is to pull with
docker.io/<repo>/<app>
In your case, try
docker.io/docker/whalesay