Ryuk failed to start (with lima)

[varpa89]

Mac Os BigSur 11.6.3 Intel
org.testcontainers:postgresql:1.16.3

I use lima 0.8.2 with docker

Client: Docker Engine - Community
 Version:           20.10.12
 API version:       1.41
 Go version:        go1.17.5
 Git commit:        e91ed5707e
 Built:             Sun Dec 12 06:28:24 2021
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.12
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.12
  Git commit:       459d0df
  Built:            Mon Dec 13 11:43:41 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.12
  GitCommit:        7b11cfaabd73bb80907dd23182b9347b4245eb5d
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

DOCKER_HOST=unix:///Users/varpa89/.lima/default/sock/docker.sock
Looks like when Testcontainers tries to run Ryuk it uses wrong Docker daemon or I understand it wrong?

At the end I have

Caused by: com.github.dockerjava.api.exception.NotFoundException: Status 404: {"message":"No such container: 8de66959ff20ff4f6a16b5f08e7bac732eae1b91b62b7ff3d816e666c4c82945"}

Detailed startup logs of Spring Boot aplication

2022-02-13 20:05:17.069  INFO 99607 --- [    Test worker] o.t.d.DockerClientProviderStrategy       : Found Docker environment with Environment variables, system properties and defaults. Resolved dockerHost=unix:///Users/varpa89/.lima/default/sock/docker.sock
2022-02-13 20:05:17.070  INFO 99607 --- [    Test worker] org.testcontainers.DockerClientFactory   : Docker host IP address is localhost
2022-02-13 20:05:17.181  INFO 99607 --- [    Test worker] org.testcontainers.DockerClientFactory   : Connected to docker: 
  Server Version: 20.10.12
  API Version: 1.41
  Operating System: Ubuntu 21.10
  Total Memory: 3919 MB
2022-02-13 20:05:17.185  INFO 99607 --- [    Test worker] o.t.utility.ImageNameSubstitutor         : Image name substitution will be performed by: DefaultImageNameSubstitutor (composite of 'ConfigurationFileImageNameSubstitutor' and 'PrefixingImageNameSubstitutor')
2022-02-13 20:05:17.248  INFO 99607 --- [    Test worker] o.t.utility.RegistryAuthLocator          : Failure when attempting to lookup auth config. Please ignore if you don't have images in an authenticated registry. Details: (dockerImageName: testcontainers/ryuk:0.3.3, configFile: /Users/varpa89/.docker/config.json. Falling back to docker-java default behaviour. Exception message: /Users/varpa89/.docker/config.json (No such file or directory)
2022-02-13 20:05:18.665  WARN 99607 --- [    Test worker] o.testcontainers.utility.ResourceReaper  : Ryuk container cannot be inspected and probably had a problem starting. Ryuk's logs:
2022/02/13 19:05:18 Pinging Docker...
panic: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

goroutine 1 [running]:
main.main()
	/go/src/github.com/testcontainers/moby-ryuk/main.go:36 +0x457

2022-02-13 20:05:19.676 ERROR 99607 --- [    Test worker] com.zaxxer.hikari.pool.HikariPool        : HikariPool-1 - Exception during pool initialization.
java.lang.IllegalStateException: Ryuk failed to start

[handcarbon]

Setting these env variables worked for me (using Colima), so TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE might be working for lima also.

TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE=/var/run/docker.sock
DOCKER_HOST=unix:///Users/my.user/.colima/docker.sock

Most likely related to this
#5034

[kiview]

@siim-romanov 's setting should work for you, I will therefore close the. Feel free to let us know, if you still encounter problems.

[dnatic09]

@siim-romanov 's setting should work for you, I will therefore close the. Feel free to let us know, if you still encounter problems.

I actually symlinked my home-directory-colima-docker.sock to /var/run/docker.sock

/var/run/docker.sock disappeared and never came back after I uninstalled Docker Desktop.

EDIT: I deleted my symlink and used the recommended environment variables. No positive change/impact.

[abenabderrahmane]

Thanks @siim-romanov . Setting env variable TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE did the trick for me.

[MartinAhrer]

Even though this is already closed I don't really think this has been answered properly. I did some debugging in the test containers code to understand the environment variables to configure a non Docker Desktop environment such as lima (and probably colima as well).
I understand that many have to switch from the great Docker Desktop offering for various reasons and I have been affected by that as well.

The solution basically lies in the lima configuration file lima.yml ($HOME/.lima/lima-docker/lima.yaml) of the lima instance. This configures the socket binding of the docker daemon socket.

In my default configuration created from limactl start template://docker this is for example

portForwards:
- guestSocket: "/run/user/{{.UID}}/docker.sock"
  hostSocket: "{{.Dir}}/sock/docker.sock"

The guest socket is the socket that the docker daemon binds to inside the guest vm. ryuk is a container running in the guest instance. Hence the variable TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE should point to the socket bound in the guest instance.
The above lima configuration uses /run/user/{{.UID}}/docker.sock which in my lima instance is /run/user/501/docker.sock. For automating this it is possible to get the uid from the limactl info command.

So to get to the point configure

TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE=/run/user/501/docker.sock and adjust to the proper path for the lima instance/guest!