Menu
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"}
924
Starting from version 1.14.3 testcontainers uses ryuk from Docker Hub instead of the quay.io. So raise your testcontainers version. I got this error recently: upgrading testcontainers to version "1.15.1" fixed this issue.
If your environment already implements automatic cleanup of containers after the execution, but does not allow starting privileged containers, you can turn off the Ryuk container by setting TESTCONTAINERS_RYUK_DISABLED environment variable to true.
Note that Testcontainers will continue doing the cleanup at JVM's shutdown, unless you kill -9 your JVM process. pull.pause.timeout = 30 By default Testcontainers will abort the pull of an image if the pull appears stalled (no data transferred) for longer than this duration (in seconds).
Add checks.disable=true to your $HOME/.testcontainers.properties to completely disable them. This approach is discouraged and deprecated, but is documented for completeness. Overriding individual image names via configuration may be removed in 2021.
Starting from version 1.14.3 testcontainers uses ryuk from Docker Hub instead of the quay.io. So raise your testcontainers version.
86
I got this error recently: upgrading testcontainers to version "1.15.1" fixed this issue.
8
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
