I've been using Podman for a while, but Docker Compose feels easier to manage than Kubernetes files or Quadlets. Has anyone switched back, and what made the difference?
Has anyone gone back to Docker after using Podman?
Asked by
2m+velcrostamp.804
Answers
Compose is a pretty good reason on its own. Lots of projects provide Docker Compose files and Docker instructions, so there's less translating to do when adding or updating an app. For a home setup, that convenience can outweigh the work of maintaining Quadlets.
Reply to this answer
Have you tried podman-compose before switching? It can be an option if you want to keep Podman but use Compose files. Compatibility seems to depend on the files involved, though. Basic setups may work fine while others need changes.
Rivnor__8h:
Environment files are worth checking during a test. Differences in how quotes are handled can cause surprises.
Reply to this answer
There's also a middle ground: Podman and Quadlets can make sense where their security features and systemd integration are useful, while Docker Compose may be simpler for a small home setup. You don't have to pick one tool for every environment.
Reply to this answer
Check your actual applications before committing either way. Some packages are documented and supported specifically for Docker, and getting them running under Podman may take more effort than the container images alone suggest. Nextcloud AIO and OpenCloud were mentioned as troublesome examples, though that doesn't establish that they can never work with Podman.
Reply to this answer
For bigger deployments, Kubernetes is another direction rather than trying to make Quadlets do everything. For a few services at home, though, that could be more complexity than you need. Docker Compose is a reasonable choice if it fits the job.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Mavro-2q:
Documentation and support matter too. Some maintainers only support Docker, even when their containers can run under Podman.