←back to thread

Podman Quadlets with Podman Desktop

(podman-desktop.io)
180 points teleforce | 2 comments | 14 Apr 25 17:16 UTC | HN request time: 0.42s | source
Show context
andreldm ◴[14 Apr 25 20:10 UTC] No.43685772[source]▶
I have a RPi 2 that’s more than enough for my home server needs and I’ve tried to migrate from docker to podman, it simply failed miserably with weird errors, on my laptop everything worked fine, so maybe that’s an issue with Arch ARM or the 32-bit version of it, but really, I wish they could abstract away quadlet, service files generation and so on.
replies(1): >>43686646 #
Alupis ◴[14 Apr 25 21:43 UTC] No.43686646[source]▶
If you install the `podman-docker` package, you get compatibility with docker commands. If you have errors during runtime, it's probably something in your container/config that's assuming a docker socket/runtime. Some of which can be remedied by pointing `DOCKER_HOST` to your podman socket, etc.
replies(1): >>43689831 #
1. andreldm ◴[15 Apr 25 07:06 UTC] No.43689831[source]▶
The problem wasn’t running the containers with plain podman, they worked. Auto restart is something podman delegates to quaqlet/systemd, I tried to migrate my docker-compose files to quadlet’s config, the containers were up, supposedly listening to the bound ports but connecting simply didn’t work. I tried rootless, slirp4netns and pasta, nothing worked, then I gave up, some other day I might try again.
replies(1): >>43691359 #
2. worewood ◴[15 Apr 25 11:34 UTC] No.43691359[source]▶
Running a very similar setup here, also have issues with networking. Pasta worked, but has bugs and replied UDP packets on the wrong ports. The pasta version from debian packages is too old. Also, I tried making the networking work but now I just slap --network=host on everything and call it a day--works perfectly.