Required to login to pull public images?

[magick93]

Why is it that I am required to login to pull a public image, for example:

docker pull  wodby/drupal-php:7.1-2.4.4

Please login prior to pull:
Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.

I have never had to do this before.

[Johannestegner]

I started seeing this a couple of days ago too, but not for all images, and just for some tags on some images.

For example, I could use FROM alpine:latest in a Dockerfile but not FROM alpine:3.6.
Is this intended (I mean that we have to be logged in to pull) or is this a bug?

[v9Chris]

Had a similar issue halfway through today (pulled several times fine and then all of a sudden...)

Step 1/15 : FROM ubuntu:16.04
ERROR: Service 'wagtail' failed to build: Get https://registry-1.docker.io/v2/library/ubuntu/manifests/16.04: unauthorized: incorrect username or password

I had to docker login to get it to work, never had to login for any repo in the past and not sure why this happened halfway through multiple clean builds.

[MatMaul]

Same here. This is really annoying, especially with skopeo which just get stuck in this case.
My public image is matmaul/kubernetes-kubelet:test.
One of the problematic layer is 8b56dcf16c5ac86dc93a383f5613d6557415639104ae3d01fc00fb3226125a68 for example.

[marcusmartins]

Hi - to help us troubleshoot, can you share your Docker version?

[MatMaul]

It was with skopeo and it got stuck on this layer. I saw a 401 in debug mode.
Last skopeo version of f25.
And now of course I can't reproduce. Perhaps some eventual-consistency issues in the ACLs of the layers ?
I'll try to have a more comprehensive test case tomorrow by pushing and trying right after.

Thanks for the feedback.

[ericcurtin]

Just got this same issue:

>docker pull curtine/sxx:centos6

Please login prior to pull:
Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.
Username (curtine): ^C
> docker version
Client:
 Version:      17.05.0-ce
 API version:  1.29
 Go version:   go1.7.5
 Git commit:   89658be
 Built:        Thu May  4 22:10:54 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.05.0-ce
 API version:  1.29 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   89658be
 Built:        Thu May  4 22:10:54 2017
 OS/Arch:      linux/amd64
 Experimental: false

[ericcurtin]

I have to login for every pull at the moment for some reason?

It seemed to start when I changed my dockerhub password..

[artischocke]

Same

Client:
 Version:	17.12.0-ce
 API version:	1.35
 Go version:	go1.9.2
 Git commit:	c97c6d6
 Built:	Wed Dec 27 20:11:19 2017
 OS/Arch:	linux/amd64

Server:
 Engine:
  Version:	17.12.0-ce
  API version:	1.35 (minimum version 1.12)
  Go version:	go1.9.2
  Git commit:	c97c6d6
  Built:	Wed Dec 27 20:09:53 2017
  OS/Arch:	linux/amd64
  Experimental:	false

[ericcurtin]

A docker login fixes it... But wonder why you have to login to pull public images

[adewes]

For me the problem was that I had an (apparently expired) authentication token in my ~/.docker/config.json file, which the daemon then tried to use to pull the image from Dockerhub. Deleting the file resolved the problem. If you have the same problem try removing the file.

[ericcurtin]

@adewes thanks for the info, I suspect that's what happens in my case the authentication token was not longer valid.

I apologize for repetition but why do you need a valid auth token to pull a public image that does not require authentication?

[adewes]

@ericcurtin you don't need a valid auth token to pull a public image, but if the Docker client finds an auth token it will probably use it to pull images as I think it can't distinguish between a public and a non-public image on Dockerhub based on the image name/path alone.

You could configure the Docker client to not automatically use a credential from your home directory (https://docs.docker.com/engine/reference/commandline/login/#privileged-user-requirement), by default it seems that it will always use it though when available.

[nixbytes]

just curious why do docker need login and account info? is this required for CE edition or open source project?

[kurtfm]

A quick way to remove the old credential is to run docker logout .. if you really need to you can run docker login after that.

[luthor112]

The same problem still occurs in November 2018 on version 18.09.0.

Edit: Configuring a proxy for the Docker daemon solved the issue for me, as stated at community.ubnt.com.

[vinchauhan]

Changed the password for docker hub but the cli still cant access the public images. I tried restarting docker app on windows but still no luck. I new password works on docker hub but not on

docker login

Frustrating...!

[vinchauhan]

Changed the password for docker hub but the cli still cant access the public images. I tried restarting docker app on windows but still no luck. I new password works on docker hub but not on

docker login

Frustrating...!

It worked later when I used docker id as username and not email

[DMCHatRally]

Whether or not logged in, it won't let me pull a public Python image.

[vinchauhan]

@DMCHatRally try login with docker username and not email

[JoshBowdenConcepts]

I am running into the same issue.

[brandonfl]

Same here

Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.

On a pull of a public image ...

[punkosu]

I just noticed that if I use "centos7" I get the login error, but "centos:7" works fine. Just in case someone else runs into this same issue.

[divadsn]

As this issue still is open (although a solution has been posted, thank you @adewes), could I suggest adding a fallback, so public images can still be pulled even with an expired auth token?

[github-actions]

We are clearing up our old issues and your ticket has been open for 6 months with no activity. Remove stale label or comment or this will be closed in 15 days.

[AlbertoMQ]

This is still an issue

[ericcurtin]

I've since moved to podman and quay.io, having great joy! 😄