517
Every time I use podman (thelemmy.club)
submitted 3 weeks ago* (last edited 3 weeks ago) by to c/linuxmemes@lemmy.world
206 comments fedilink hide all child comments
 

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 (3 children)

Fair enough. My requirements are simply: start all services when the machine has finished booting. And I can't remember the last time my system failed. Most that happened was a power outage, and Quadlets wouldn't have helped there either.

So in my case I much prefer simple and easy-to-read configs, over the complexity of integrating with systemd.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 3 weeks ago (2 children)

    Docker compose definitely works for most people, so I would feel pressured to swap.

    There is one instance where Quadlets would have fixed an issue we ran into at work. We had a Kafka instance whose container died and went away because we ran out of space on the server. Compose doesn't recreate containers on failure, so I was called in to fix the issue. Quadlets treats containers as disposable, so it would have recreated it as soon as it went away. The root of the issue was a bad logging config that we fixed on the next business day.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child 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.

  • permalink
  • fedilink
  • 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.

  • permalink
  • fedilink
  • source
  • parent