I am moving from docker to podman and selinux because I thought that podman is more secure and hence, the future. I thought the transition will be somewhat seamless. I even prepaired containers but once I migrated I still ran into issues.
minor issue: it’s podman-compose instead of podman compose. The hyphen feels like a step back because we moved from docker-compose to docker compose. But thT’s not a real issue.
podman does not autostart containers after boot. You have to manually start them, or write a start script. Or create a systemd unit for each of them.
Spinning up fresh services works most of the time but using old services that worked great with docker are a pain. I am wasting minutes after minutes because I struggle with permissions and other weird issues.
podman can’t use lower number ports such that you have to map the ports outside of the machine and forward them properly.
Documentation and tutorials are “all” for docker. Github issues are “all” for docker. There isn’t a lot of information floating around.
I’m still not done and I really wonder why I should move forward and not go back to docker. Painful experience so far.
I know this isn’t the answer you want, but consider switching away from
compose
entirelyA local kubernetes instance handles all the routing for me, and since i was using that anyway podman was legitimately a drop in replacement for docker.
Podman is just the tool that creates the container for me, running it gets handled by something else entirely.
Also, i can run
podman compose up
just fine, no hyphen needed. https://docs.podman.io/en/latest/markdown/podman-compose.1.html