submitted 3 weeks ago* (last edited 3 weeks ago) by to c/linuxmemes@lemmy.world
 

EDIT: For some context, I recently gave podman another go. I have a few services on my homelab server set up in docker containers, so I tried migrating to podman.

After the second major bug (open issue on github) I encountered looked like it would require completely dropping using compose files to work around, I gave up and went back to docker.

I like the idea of podman, but it’s just not stable. I’ll try again in a year or so.

As a bonus, docker’s CLI is significantly nicer.

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 3 weeks ago* (1 child)

Compose doesn't recreate containers on failure

Isn't it just restart: always in the config? Unless you're talking about podman, where you also need the podman-restart systemd service.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 3 weeks ago

    You are correct that they restart a container that has stopped because of a bad exit. I meant a container that has completely disappeared due to running out of storage on the system. Given, that is a failure of configuration to begin with.

  • source
  • parent