Repository navigation
[Bug]: Ryuk does not start with Colima #12104
Description
Module
Core
Testcontainers version
1.21.4
Using the latest Testcontainers version?
Yes
Host OS
MacOS Golden Gate
Host Arch
aarch64
Docker version
Docker version 29.8.2, build 7fc2dff9bcWhat happened?
My issue might be similar to this one: #7082
I noticed that some of my tests fail, those are Java tests that provision a DB through testcontainers.
They fail with lots of failed connection attempts to ryuk.
I tried to debug my setup but did not find the issue so far. I did figure out that apparently ryuk does not start at all.
docker run testcontainers/ryuk:0.14.0
Unable to find image 'testcontainers/ryuk:0.14.0' locally
0.14.0: Pulling from testcontainers/ryuk
Digest: sha256:7c1a8a9a47c780ed0f983770a662f80deb115d95cce3e2daa3d12115b8cd28f0
Status: Downloaded newer image for testcontainers/ryuk:0.14.0
2026/10/05 14:20:31 ERROR run error="new reaper: ping: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"
It does seem to work for others using Docker Desktop. I use colima version 0.10.3 and followed all the instructions here: https://java.testcontainers.org/supported_docker_environment/#colima
I did try to run other containers and they start up just fine, for example Ubuntu.
Any ideas what I can try to make it work?
Relevant log output
16:59:04.766 [testcontainers-ryuk] WARN org.testcontainers.utility.RyukResourceReaper -- Can not connect to Ryuk at 192.168.64.2:32772
java.net.NoRouteToHostException: No route to host
at java.base/sun.nio.ch.Net.connect0(Native Method)
at java.base/sun.nio.ch.Net.connect(Net.java:546)
at java.base/sun.nio.ch.Net.connect(Net.java:535)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:585)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:284)
at java.base/java.net.Socket.connect(Socket.java:659)
at org.testcontainers.utility.RyukResourceReaper.lambda$maybeStart$0(RyukResourceReaper.java:92)
at org.rnorth.ducttape.ratelimits.RateLimiter.doWhenReady(RateLimiter.java:27)
at org.testcontainers.utility.RyukResourceReaper.lambda$maybeStart$1(RyukResourceReaper.java:88)
at java.base/java.lang.Thread.run(Thread.java:1474)
Additional Information
No response
Activity
S2Philipp commentedon Oct 6, 2026
After further investigation, it does not seem to be a Ryuk but a general connection issue.
Disabling Ryuk did not solve the issue, running Ryuk priviliged did not either.
I am not sure what caused it, but I think I got it solved by running colima delete --data. Then colima start took much longer than before and it seems to be working now. Not sure what changed.
Sorry about the ticket.