Oddly enough: SELinux and file ownership for bind mounts were pretty hellish for me, even with :z. Granted, that’s definitely on me (skill issue) for having misconfigured SELinux policies, but docker got out of my way.
Other than that, my gripes about podman have to do with inter-container DNS communication and having to creating systemd services to manage simple container stacks. That last one is a major thorn in my side because the podman CLI used to have a simple command to generate the systemd file for you, but they’re getting rid of it.
I run containers locally for basic dev work and, on occasion, deploy simple self-hosted services. In both of those cases, I find Podman to be an unnecessary hindrance where Docker isn’t.
It’s foolish to remove a tool to generate systemd files, running containerized services is one of the main uses of tools like these. That is a big disappointment.
Oddly enough: SELinux and file ownership for bind mounts were pretty hellish for me, even with
:z. Granted, that’s definitely on me (skill issue) for having misconfigured SELinux policies, butdockergot out of my way.Other than that, my gripes about
podmanhave to do with inter-container DNS communication and having to creating systemd services to manage simple container stacks. That last one is a major thorn in my side because thepodmanCLI used to have a simple command to generate the systemd file for you, but they’re getting rid of it.I run containers locally for basic dev work and, on occasion, deploy simple self-hosted services. In both of those cases, I find Podman to be an unnecessary hindrance where Docker isn’t.
deleted by creator
It’s foolish to remove a tool to generate systemd files, running containerized services is one of the main uses of tools like these. That is a big disappointment.