Cannot pull images when logged in to Docker Desktop (Status 500: unauthorized: incorrect username or password)

[MH-17]

Test Containers 1.16.3 on Docker Engine 20.10.12 with Docker Desktop using WSL2 Backend on Windows 21H1.

When I am logged in to my account in Docker Desktop, Test Containers can no longer pull images from Docker Hub. Once I log out of my account, Test Containers is able to pull images as expected.

com.github.dockerjava.api.async.ResultCallbackTemplate - Error during callback
com.github.dockerjava.api.exception.InternalServerErrorException: Status 500: {"message":"Head \"https://registry-1.docker.io/v2/testcontainers/ryuk/manifests/0.3.3\": unauthorized: incorrect username or password"}
	at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.execute(DefaultInvocationBuilder.java:247)
	at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.lambda$executeAndStream$1(DefaultInvocationBuilder.java:269)
	at java.base/java.lang.Thread.run(Thread.java:833)

I think my Docker installation is fine, as I can pull images from the terminal when I am logged in to Docker Desktop. I don't want to log out every time I use Test Containers. How can I fix this issue?

Logs (on INFO): https://pastebin.com/fyExxi76

Logs (on DEBUG): https://pastebin.com/b4H283fL

[luedi]

I have exactly the same issue with Test Container 1.16.2. This issue only occurs if the Docker image has to be pulled. As long as I have a local image everything is fine.

[awojcik64]

Problem still exists with Test Containers 1.16.3 and Docker Desktop with versions: 4.2.0, 4.3.2, 4.6.1 and 4.7.0
Actually, it happens regardless if I'm logged in or not.

12:21:49.321 [main] INFO  org.testcontainers.utility.ImageNameSubstitutor - Image name substitution will be performed by: DefaultImageNameSubstitutor (composite of 'ConfigurationFileImageNameSubstitutor' and 'PrefixingImageNameSubstitutor')
12:21:49.368 [main] INFO  org.testcontainers.dockerclient.DockerClientProviderStrategy - Loaded org.testcontainers.dockerclient.NpipeSocketClientProviderStrategy from ~/.testcontainers.properties, will try it first
12:21:49.854 [main] INFO  org.testcontainers.dockerclient.DockerClientProviderStrategy - Found Docker environment with local Npipe socket (npipe:////./pipe/docker_engine)
12:21:49.854 [main] INFO  org.testcontainers.DockerClientFactory - Docker host IP address is localhost
12:21:49.888 [main] INFO  org.testcontainers.DockerClientFactory - Connected to docker: 
  Server Version: 20.10.14
  API Version: 1.41
  Operating System: Docker Desktop
  Total Memory: 51188 MB
12:21:55.569 [docker-java-stream--301690517] ERROR com.github.dockerjava.api.async.ResultCallbackTemplate - Error during callback
com.github.dockerjava.api.exception.InternalServerErrorException: Status 500: {"message":"Head \"https://registry-1.docker.io/v2/testcontainers/ryuk/manifests/0.3.3\": unauthorized: incorrect username or password"}

Image pulled manually via docker pull testcontainers/ryuk:0.3.3 works just fine. It's just a workaround though.

[kiview]

Thanks for bumping this issue. I was recently running into this error on Docker Desktop as well.
Can you please try out to logout and then perform the Docker login on the command line instead (docker login)?

And can someone reproduce this with Docker Desktop on macOS as well?

[SiwyDym]

I tested on 4.3.2 on macOS(12.1 (21C52)) and it's looking like a charm, but for Windows I encountered the same issue as @awojcik64

[awojcik64]

I don't know how I did that, but now containers are pulled correctly even if I am logged out of everything.
I was only juggling logging in using GUI and command line. (tested on Docker Desktop 4.7.0)

[kiview]

@awojcik64 How I perceive the error so far with regards to pulling public images with Testcontainers:

• Docker Desktop did the login through the GUI: not working ❌
• Docker login through CLI and username/pw (docker login): working ✅
• Docker logged out: working ✅

For further triangulation, may I ask you @SiwyDym if you are sure that on macOS, you recently did a login through the Docker Desktop GUI and it still worked? Also, please make sure the images are not cache before trying out Testcontainers.

So as a current workaround, I'd suggest doing the docker login from CLI instead of the GUI and everything should work fine.

[SiwyDym]

I can confirm that issue occurs when I login by Docker Desktop GUI :|
Docker Desktop: 4.7.0 (77141)
OS: 12.1 (21C52)

[kiview]

@SiwyDym Can you confirm that performing the login through CLI mitigates the issue?

[SiwyDym]

I cannot confirm that, the only working mitigation for me is manually pulling the image testcontainers/ryuk:0.3.3

[kiview]

@SiwyDym I see. Can you instead confirm that it works if your Docker daemon is unautheticated? (after docker logout)

[kiview]

Another interesting aspect to try out is if doing a docker login registry.hub.docker.com mitigates the situation.