3 ms·
Can anyone explain what daemonless means in this case and what the advantages are? (I don't work in this space and my knowledge ends with knowing what a contain
by superbcarrot 6y ago
Can anyone explain what daemonless means in this case and what the advantages are? (I don't work in this space and my knowledge ends with knowing what a container is.)
- _joel 6y agoYou don't need root access to run the containers
- 8fingerlouie 6y agoIIRC, docker by default runs a daemon as root, which spawns all your containers. It is possible to run it rootless as well (https://docs.docker.com/engine/security/rootless/ https://docs.docker.com/engine/security/rootless/), though you’d need a separate daemon for each user you’d want to run containers as. Podman doesn’t have that. It spawns containers without the help of a controlling daemon, and can spawn containers both as root and rootless. Rootless is of course a fairly big deal considering if you run docker containers as root, and runc has a vulnerability, you could potentially escape the container and become root, where a rootless installation would just let you escape to whatever user is running the container.
- mekster 6y agoSo, it's only about a tiny security concern but it got much bigger usability problems and what's worse RedHat is forcing people to use podman since RHEL 8 when it's not even ready.