You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can SSH into the container. But docker info says docker is not running. I also don't see docker in ps aux and all files in /config/logs/dockerd/ are empty. s6 seems to be doing some things (there's a s6-supervise svc-mod-universal-docker-in-docker), but I do not know what this means.
If anyone has any documentation how to debug s6, that be very welcome. Usually I would try to stop the service, start it manually and maybe enable verbose output. But I've never been able to figure out how to do that with s6.
Expected Behavior
Docker should be running in the container. This is on AMD64, in case it matters. Is there any documentation on how this DIND works? Documentation talks about QEMU, does that mean I somehow have to enable nested virtualization? Or will this mod use software QEMU and be slow?
Small update: What I wanted to do ultimately was set up an SSH server with a distrobox instance. This way I can ssh into the basic linuxserver container (which can be kept up-to-date by pulling new docker images) and run any other distro with full package access using distrobox.
I wanted to use docker for this, but it seems this whole setup is way easier to manage using podman. I just use the universal-package-install mod now and let it install distrobox, which also installs podman. I then mount the /etc/subuid and /etc/subgid files as volumes, as they need to be configured for podman. Additionally, the openssh-server container has to run in privileged mode. And that's it, with these changes distrobox works fine.
So although this bug report is still valid, I'd recommend just using podman instead.
Is there an existing issue for this?
Name of mod
svc-mod-universal-docker-in-docker
Name of base container
linuxserver/openssh-server
Current Behavior
When starting the container, after package installation I just get these messages:
I can SSH into the container. But docker info says docker is not running. I also don't see docker in
ps aux
and all files in/config/logs/dockerd/
are empty. s6 seems to be doing some things (there's as6-supervise svc-mod-universal-docker-in-docker
), but I do not know what this means.If anyone has any documentation how to debug s6, that be very welcome. Usually I would try to stop the service, start it manually and maybe enable verbose output. But I've never been able to figure out how to do that with s6.
Expected Behavior
Docker should be running in the container. This is on AMD64, in case it matters. Is there any documentation on how this DIND works? Documentation talks about QEMU, does that mean I somehow have to enable nested virtualization? Or will this mod use software QEMU and be slow?
Steps To Reproduce
Using this compose file:
docker-compose up
produces the error message.Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: