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. https://linuxhandbook.com/docker-vs-podman/ and following pages helped me a lot to get rid of my frustration with podman.

  • @[email protected]
    link
    fedilink
    English
    19 months ago

    podman does not autostart containers after boot.

    Does docker do this? I wrote a systemd unit for my docker container because I thought that there is no way for docker to autostart containers?

    • @Molecular0079
      link
      English
      119 months ago

      It does. You probably did not enable docker.service to start on boot.

    • @ikidd
      link
      English
      59 months ago

      Not sure about straight docker run commands, but if you’re using docker compose you can add restart: unless-stopped or always to your docker-compose.yml to have it come up on boot.