Also, another benefit of podman is that it doesn't use the client-server model, it's just fork+exec no daemon needed. Dan has a bunch of talks that are great introductions to podman and container security in general:
- https://www.youtube.com/watch?v=ZE2nI1SwSVk
- https://www.youtube.com/watch?v=msdaf3lBOn0
- https://www.youtube.com/watch?v=YkBk52MGV0Y
- https://www.youtube.com/watch?v=40ynATurI7k
[EDIT] - I did not realize that non-root podman was a 1.0 feature -- as others have noted, podman <1.0 required sudo.
That should change as rootless matures.
Second thing -- I haven't looked into it much but do you know how the docker in docker support is in podman? Is this thread (https://github.com/containers/libpod/issues/746) the right one to watch?
My understanding is that many, if not most, operations should not require sudo as of version 1.0.
For example, try the commands at https://github.com/containers/libpod/blob/master/docs/tutori...
Would be nice if someone developed a testsuite that exercises all the usual FS operations that a container uses (permissions, setuid, setcap, symlinks, etc.) and compares vfs vs fuse-overlayfs vs in-kernel overlayfs vs docker?
See this article for more details https://opensource.com/article/18/10/podman-more-secure-way-...
I'm extrapolating that an advantage of Podman is that it should not require root permissions. But almost every call to podman in the article involves sudo. Can anyone clarify?