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.
Related
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?
After using Docker for almost two months, today I got the following error:
C:\Users\dell>docker --version
Docker version 17.06.0-ce, build 02c1d87
C:\Users\dell>docker ps -a
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.30/containers/json?all=1:
open //./pipe/docker_engine: The system cannot find the file
specified. In the default daemon configuration on Windows, the docker
client must be run elevated to connect. This error may also indicate
that the docker daemon is not running.
Yes, the daemon is running, or at least it is shown as running under Services. I use it only with a local container and do not do anything remote.
Any suggestions on how this can be solved?
Well, I have had the same issue today and the only way for me to fix it was by reinstalling Docker (uninstall and install latest stable version)...
Now docker info runs OK and my solution builds again.
I hope it helps,
Juan
Note: it shouldn't have happened at all, I've lost at least one hour trying to figure out what and why it crashed...
Is Hyper-V running? You will get this error if Hyper-V closes down. Docker for Windows will still be "running", but the daemon will not work.
I'm trying to check the installation docker pull hello-world
But getting the following error:
Pulling repository hello-world
Get https://index.docker.io/v1/repositories/library/hello-world/images: remote error: access denied
I have CentOS 6.5
Docker version 1.7.1, build 786b29d/1.7.1
I'm in a corporate network but curl https://index.docker.io/v1/repositories/library/hello-world/images forks fine.
What might be the issue?
Thanks in advance!
I got this error while I was trying to pull mongodb image instead of mongo.
So make sure image name is correct. The very same error message happens on both run and pull commands.
Had the same problem & error on the host working via proxy.
In essence - if you are behind an HTTP proxy server, you will need to add proxy configuration in the Docker systemd service file.
https://docs.docker.com/engine/admin/systemd/
(See at "HTTP proxy" section).
This helped me.
Did you add your user in docker group
https://docs.docker.com/engine/installation/linux/centos/#/create-a-docker-group
Otherwise, you should execute docker command with sudo before
docker pull hello-world
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.
i am trying to push a image to myown docker registry.I got invalid endpoint registry error.When i googled it i got solution of running these commands.This is the link Remote access to a private docker-registry when i try to run first command i.e service docker stop i will get always service is not recognised.Rest other docker commands run fine.I googled it but not getting much help.If any one can help me how to solve this problem?
Is it because you installed docker.io so the service is called docker.io?
Does service docker.io stop work?
See https://docs.docker.com/installation/ubuntulinux/ for how to get a much newer version.