Closed Sereja313 closed 7 months ago
I also noticed that despite the fact that the config has a configCreateReaper
field that allows you to set your own reaper container, at the moment the user cannot define their own reaper container since the library does not provide a method for modifyingnoReaper
field of ContainerRequest
. Perhaps skipReaper
or something like setNoReaper
should be exported by the library.
@Sereja313 I provided your suggestion in https://github.com/testcontainers/testcontainers-hs/pull/48.
Great! Thank you!
Problem: The reaper container currently expects a docker socket to be available at
/var/run/docker.sock
, but this is not always the case. Especially with rootless docker, which usually puts the socket at$XDG_RUNTIME_DIR/docker.sock
and then exports it asDOCKER_HOST=unix://$XDG_RUNTIME_DIR/docker.sock
. In this case, the reaper container will not be able use docker.Solution: Check if the
DOCKER_HOST
environment variable sets the docker socket location to something other than the default.