{ "@context":[ "https://www.w3.org/ns/activitystreams", {"Hashtag":"as:Hashtag"} ], "published":"2024-10-23T19:03:00.705Z", "attributedTo":"https://sup.f5n.org/actors/wink", "replies":"https://sup.f5n.org/objects/lBgKplc1iU8/replies", "to":["https://www.w3.org/ns/activitystreams#Public"], "cc":["https://sup.f5n.org/actors/wink/followers"], "content":"

I know I should properly blog this, but meh.

On one server for a project I wanted to try podman, you know rootless containers, not Docker, etc.

It looked ok at first although it was a bit tedious to set up.

But either I am holding it wrong or it's just vastly inferior. Every time I reboot the whole setup just dies and I have to do `podman-compose down && podman-compose up -d` unlike with `docker-compose`. How often do you reboot? Not that big of a problem.

But also DNS doesn't work properly, so I can't use the DB container's hostname, I have to manually edit the IP into the config every time I redo this setup. Not great. There's an open issue on github somewhere, don't have the link handy, so it's not \"clearly my fault\".

The worst thing is though that it suddenly stops working from time to time, without a reboot, and I have to do a `loginctl enable-linger <int>` before I can do anything, although it tells me to do `podman system migrate` or something, which never works.

Yeah, I guess I should RTFM some more, but this is clearly either broken or at least kinda hard to use with at least some documentation bugs or huge caveats.

", "mediaType":"text/html", "attachment":[], "type":"Note", "id":"https://sup.f5n.org/objects/lBgKplc1iU8" }