Today I made the difficult decision to switch back to Docker instead of Podman. It’s nice and all but, for production use, it’s just not “there” yet. It’s too clunky that it’ll take me quite some time to reform my workflow just to adapt to it’s clunkiness. Maybe I’ll try again in the future but, for now, Podman’s just not doing it for me. I’ll list some of my gripes below just to serve as a reference to myself in the future:
- podman compose up -d can’t do an intelligent recreate when a newer image is available and there’s pod dependencies. Passing the “–recreate” argument to podman isn’t a solution since it’ll just recreate everything everytime I issue the command.
- Generating systemd service files are nice and all, but it doesn’t seem to work on pods created by a compose! Now, I made it work and all but that still took some time for me to do when it should’ve been seamless. The fact that it can’t intelligently exclude things is just a pain. My services are quite simple but it just throws everything in the service unit that it makes it not work when you try to start the service.
Hopefully, in the future, the above won’t be a problem. If it still is, I’d rather stick to Docker and wait for when Kubernetes becomes more friendly as well.
Leave a Reply