3 ms·
Disclaimer: I work for Red Hat which is the main force behind Podman I mostly agree, however I don't think saying that Podman lacking a docker.sock is a lack
by freedomben 6y ago
Disclaimer: I work for Red Hat which is the main force behind Podman
I mostly agree, however I don't think saying that Podman lacking a docker.sock is a lack of feature parity, since that's actually considered a feature of Podman. The daemon model that Docker uses has security implications that are non-trivial. Podman chooses not to be a daemon by choice. There is a sister project called CRI-O that has a daemon which will get you the daemonized portion if that's what you want. It has a similar API and a CLI called crictl to drive it. It's not widely used outside of Kubernetes, but it is available if you want it. If you're trying to compare apples to apples, it should be docker vs podman/cri-o, not docker vs podman.
Podman also has some features that Docker does not have, such as the ability to create, run, and export Pods (same YAML definition as Kubernetes, which is mighty convenient).
I used to use docker-compose all the time, but I've found I largely don't need it anymore since I can put the various dev services into the same Pod. This is even more convenient since from every container you can just reference "localhost" since the Pod shares a network namespace between containers. It's not a perfect solution though, and certainly isn't a drop-in for docker-compose (although nobody working on Podman has claimed it is, either).
All that said Docker still has it's place. There are tools that need the docker sock in order to work. One that I wrote (called Dory[1]) is a good example of one that won't work on Podman/CRI-O without significant work.
[1]: https://github.com/freedomben/dory https://github.com/freedomben/dory