This is actually perfect. My main issue with EL distros is that they tend to push podman, which is not a 1-to-1 replacement for docker. This may end up being my default for non-immutable OS installs.
I'm trying to learn Podman because Fedora atomic is the way I want to go right now, but getting firewalld to cooperate is enraging. Are you hitting problems other than that?
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.
Try deploying the Bitwarden self-hosted stack (official, not Vaultwarden) with Podman and then you'll see that Podman's inter-container DNS isn't up-to-par with Docker's.
Podman is not a perfect replacement for Docker and often times gets in the way.
7 Comments
fox2263@lemmy.world · 5 pts · 2y
Another week. Another distro.
Fine. I’ll add it to my collection.
admin@discuss.online · 1 pts · 2y
ProdigalFrog@slrpnk.net · 3 pts · 2y
Could be an interesting base for DistroBox.
avisf@feddit.org · 2 pts · 2y
trevor@lemmy.blahaj.zone · 2 pts · 2y
This is actually perfect. My main issue with EL distros is that they tend to push podman, which is not a 1-to-1 replacement for docker. This may end up being my default for non-immutable OS installs.
barsquid@lemmy.world · 3 pts · 2y
I'm trying to learn Podman because Fedora atomic is the way I want to go right now, but getting firewalld to cooperate is enraging. Are you hitting problems other than that?
trevor@lemmy.blahaj.zone · 2 pts · 2y
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.
barsquid@lemmy.world · 2 pts · 2y
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.
avisf@feddit.org · 2 pts · 2y
admin@discuss.online · 1 pts · 2y
trevor@lemmy.blahaj.zone · 0 pts · 2y
Try deploying the Bitwarden self-hosted stack (official, not Vaultwarden) with Podman and then you'll see that Podman's inter-container DNS isn't up-to-par with Docker's.
Podman is not a perfect replacement for Docker and often times gets in the way.
admin@discuss.online · 1 pts · 2y