Replies: 3 comments 3 replies
-
You would need to disable selinux for the container if you want to leak the podman socket, i.e. |
Beta Was this translation helpful? Give feedback.
-
Yes SELinux will block communications between a container and any socket leaked into the container. Whether this is Docker.sock or podman.sock or any other socket for that matter. |
Beta Was this translation helpful? Give feedback.
-
Docker is probably not enforcing SELinux while Podman is. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Issue Description
Ryuk container[1] which is essential for testcontainers library can not be started when using podman.
[1] https://hub.docker.com/r/testcontainers/ryuk
Steps to reproduce the issue
This works(I use custom docker socket for clarity):
docker -H unix:///var/opt/custom/docker.sock run -v /var/opt/custom/docker.sock:/var/run/docker.sock -e RYUK_PORT=8080 -p 8080:8080 docker.io/testcontainers/ryuk:0.5.1
This does not:
podman -H unix:///run/user/1000/podman/podman.sock run -v /run/user/1000/podman/podman.sock:/var/run/docker.sock -e RYUK_PORT=8080 -p 8080:8080 docker.io/testcontainers/ryuk:0.5.1
Describe the results you received
Describe the results you expected
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Podman runs on an ordinary physical machine (laptop)
Additional information
Docker is run on a cloud VM, docker info (
$ docker -H unix:///var/opt/custom/docker.sock info
) results:Beta Was this translation helpful? Give feedback.
All reactions