Testcontainers can't pull ryuk image: quay.io is not reachable

Question

I have been experiencing issue with testcontainers failing to pull "ryuk" image from quay.io.

[32m01:23:19.732[0;39m [35m[main][0;39m [39mDEBUG[0;39m [36mo.t.d.a.AuthDelegatingDockerClientConfig[0;39m - Effective auth config [null] 
[32m01:23:30.281[0;39m [35m[tc-okhttp-stream-308592104][0;39m [1;31mERROR[0;39m [36mc.g.d.a.async.ResultCallbackTemplate[0;39m - Error during callback 
com.github.dockerjava.api.exception.InternalServerErrorException: {"message":"Get https://quay.io/v2/testcontainers/ryuk/manifests/0.2.3: received unexpected HTTP status: 500 Internal Server Error"}

user_355438 · Answer

Starting from version 1.14.3 testcontainers uses ryuk from Docker Hub instead of the quay.io. So raise your testcontainers version.

user_1567005 · Answer

I got this error recently: upgrading testcontainers to version "1.15.1" fixed this issue.

user_3315474 · Answer

The workaround is to use different ryuk container from DockerHub (https://hub.docker.com/r/testcontainersofficial/ryuk or https://hub.docker.com/r/qminder/moby-ryuk) by setting property in testcontainers property file src/test/resources/testcontainers.properties:

ryuk.container.image=testcontainersofficial/ryuk

Another option is to disable Ryuk in Testcontainers by setting environment variable TESTCONTAINERS_RYUK_DISABLED to true as described here.

user_7681696 · Answer

In my case, I have solved this problem cleaning all my docker-images.

However, upgrading, my POM.XML, to test containers 1.15.1, already, is a solution to his trouble.

user_695455 · Answer

I had the same issue and I solved it by upgrading testcontainers to version 1.16.0

Testcontainers can't pull ryuk image: quay.io is not reachable

5 Answers