I tried replacing some components of my NAS server that were on docker/docker-compose with podman but unfortunately it was not a 100% drop-in replacement. I had networking issues in podman that I did not have in docker.

The network stack is implemented quite differently in podman than in docker, once you start using more advanced features the backward compatibility disappears.

Since it came second, I think it has a lot of technical advantages, avoiding docker's mistakes and what not. In the long term I'll probably switch to it, unless Redhat keeps shooting itself in the foot...

I was scrolling through and this caught my eye but I totally misread it on first glance, I thought you typed "Pokemon is a demon" and I had to stop and scroll back cuz I was like oh shit this is going to be a good thread.

I exclusively use podman instead of docker at work and at home and haven't encountered any unsolvable problems.

I tried a couple of times to get Docker running rootlessly on my local machine, without just granting root-like permissions to the user. Spent a few hours reading just the worst documentation that tells you to do things with absolutely no explanation of why, feeling like an idiot.

Then I installed Podman. It worked more-or-less out of the box, and I got on with the rest of my project.

Docker has rootless containers, too, although I think Podman has slightly better options for unprivileged uid management.

Daemonless is appealing, especially for low-powered servers. Getting rid of Docker's background resource usage is the main reason Podman is on my to-do list.

I imagine pods could be handy to reduce network configuration for related services.

I like that the tools exist to make Podman a drop-in replacement for Docker, including the building of containers.

I have no interest in systemd; I hope it's optional.

I generally prefer podman to docker at this point for the reasons you stated. However, podman is not 100% compatible with docker, and I have run in to issues with a few tools, that were admittedly poorly written. Mostly around how they deal with file permission when move files in and out of containers.

Works great. You can even make it pretend to be Docker so you can use the Docker commands.

Ive been using podman on my nas, and i like it.
It has its issues, but knowing your containers dont run as root just makes me feel more at ease. I dont really understand why a docker should run as root, if the software in the container often run as their own user...

It's pretty cool. I yeeted docker and now use podman instead.

We are trying to use podman as a way to run Testcontainers and build images on a kubernetes cluster using Gitlab CI. Building works, but running Testcontainers doesn't so far :(

Using it on multiple servers and in small scale prod deployment. Works like a charm.

podman-compose is also usable although noticeably unfinished.