I have encountered a problem a few days ago and it drives me crazy. I have few services running on gitlab-ci.
A few days ago when, i tried to i run "docker-compose pull" or "docker pull image:version" and it failed. The weird thing is that nothing changed and it worked so far. For some services it says pull access denied because it requires docker login or repository does not exist. I run docker login before making pull, images exist and repository too. I don't understand. This is what happens when I run docker-pull compose. Docker pull is a success for some of them.
enter image description here
Related
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
FYI - This all works when run on a Mac, but I am wanting to run on Windows.
I am running the following commands from IntelliJ terminal:
1 - docker login (logging in with my credentials and getting the success message)
2 - docker-compose up (to create and start the container)
However upon running the second command, I am greeted with:
Pulling marklogic (xxxxxxx:latest)...
ERROR: pull access denied for ..., repository does not exist or may require 'docker login'
I have searched the forums and found nothing to explain what is going wrong, other than my colleagues explanation that Windows is rubbish.
Any help would be appreciated.
Some extra info:
docker -v
Docker version 17.12.0-ce, build c97c6d6
docker-compose -v
docker-compose version 1.18.0, build 8dd22a96
Well pressassociation/faux-uds-marklogic isn't in DockerHub, so I guess you have to build that first yourself, or make sure your are pointing at an internal company repository that someone else has pushed the image to.
Perhaps it works on the Mac because a docker login has been made to an internal registry before running the docker-compose up ?
Do you use your own registry (docker-registry.xxx) in your project?
I'm trying sudo docker pull ubuntu on Docker 1.13.1 on Ubuntu 16.04.2 LTS and getting error:
Error response from daemon: manifest for ubuntu:latest not found
I don't use proxy so I have no idea where manifest got lost.
Well, it just started working 3 hours later without any intervention, so I make a conclusion that the problem was caused by Docker Hub incident.
This is caused by S3 outage, see docker- issue.
For some reason Docker haven't noticed yet, according to status.
Funny thing is that one can see other services unavailable like GitHub or Travis CI.
I'm at my wits trying to get Docker images from Google Container Registry onto a Google Compute Engine instance. (The images I need have been successfully uploaded to GCR.)
I've logged in using gcloud auth login and then tried gcloud docker pull -- us.gcr.io/app-999/app which results in ERROR: (gcloud.docker) Docker is not installed..
I've tried to authenticate using oauth and pulling via a normal docker call. I see my credentials when I look at the file at .docker/config.json. Doing that, it looks like it's going to work, but ultimatly ends like this:
mbname#instance-1 ~ $ docker pull -- us.gcr.io/app-999/app
Using default tag: latest
latest: Pulling from app-999/app
b7f33cc0b48e: Pulling fs layer
43a564ae36a3: Pulling fs layer
b294f0e7874b: Pulling fs layer
eb34a236f836: Waiting
error pulling image configuration: unauthorized: authentication required
which looks like progress, because at least it attempted to download something.
I've tried both of these things on my local machine as well and both methods were successful.
Am I missing something?
Thanks for your help.
P.S. I've also tried loading a container from another registry (
Docker Hub) and that worked fine, but I need more than one container and want to keep expenses down.
After contacting Google support they informed me that there is a bug in the CoreOS gcloud alias. This bug is fixed by overwriting the alias in the shell as follows:
alias gcloud='(docker images google/cloud-sdk || docker pull google/cloud-sdk) > /dev/null;docker run -t -i --net=host -v $HOME/.config:/.config -v /var/run/docker.sock:/var/run/docker.sock -v /usr/bin/docker:/usr/bin/docker google/cloud-sdk gcloud'
I've tried this and it works now.
docker should be included in the latest versions of gcloud. You can update to the latest version of gcloud by running gcloud components update
I'm new to docker and have followed the installation instructions on their site here.
The installation completed successfully:
docker -v
Docker version 1.8.1, build d12ea79
but when I try to run
sudo docker run hello-world
I get the following:
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
535020c3e8ad: Pulling fs layer
af340544ed62: Layer already being pulled by another client. Waiting.
af340544ed62: Layer already being pulled by another client. Waiting.
This then continues to hang indefinitely.
I have tried restarting the service and my entire machine. I always get the same problem.
Any idea what's causing this or how to resolve?
This command helped on my end on Ubuntu 14.04 (Docker version 1.8.1, build d12ea79):
sudo restart docker
This seems to have now resolved itself. Quite possibly it was caused by a problem at docker's end.