A couple of reasons - I switched from Pop! OS to OpenSUSE Tumbleweed, and the Docker version in the repository is 24.07 compared to 25.02 (the current version of Docker) with the official Docker site only supporting SLES on s390x, not Tumbleweed on x86_64. The main reason though is that it can run without root which is appealing; apparently I have a lot to learn on setting that up. The glib statements of ‘drop in replacement’ that I"ve seen isn’t quite accurate apparently outside of the commandline options.
Comment on Podman - container exits without logs
faethon@lemmy.world 8 months ago
just curious; why would you like to use podman over docker? I have a lot of docker containers running, wondering if I should switch to podman.
bravemonkey@lemmy.ca 7 months ago
vojel@discuss.tchncs.de 8 months ago
No daemon needed, better security because of rootless approach, but well docker also runs rootless nowadays. Podman came up from frustration from Red Hat over docker, that’s why they developed their own thing. Afaik it is nearly full compatible and can be used as a drop in replacement for docker.
faethon@lemmy.world 7 months ago
interesting! So I should be able to throw my docker-compose yamls directly at Podman and be good to go?
poVoq@slrpnk.net 7 months ago
No, docker-compose is where Podman differs. There are some 3rd party attempts to make it compatible via podman-compose, but most people agree that the Systemd integration of Podman is better anyways and if you really need advanced orchestration then you can use K8 helmcharts with Podman.
vojel@discuss.tchncs.de 7 months ago
That is not true anymore. podman-desktop.io/docs/compose/running-compose