podman-compose is different from docker-compose. It runs your containers in rootless mode. This may break certain containers if configured incorrectly. This is why I suggested podman-docker, which allows podman to emulate docker, and the native docker-compose tool. Then you use sudo docker-compose to run your compose files in rootful mode.
Comment on PSA: Docker nukes your firewall rules, and replaces them with its own.
Link@rentadrunk.org 8 months agoIs it? Last time I tried none of my docker compose files would start correctly in podman compose.
Molecular0079@lemmy.world 8 months ago
warmaster@lemmy.world 8 months ago
How is Podman rootful better than Docker? I was mostly attracted by the rootless path, but the breakage deterred me. Would you be so kind to tell me ?
Molecular0079@lemmy.world 8 months ago
It isn’t that much better. I use it as drop-in docker replacement. It’s better integrated with things like cockpit though and the idea is that it’s easier to eventually migrate to rootless if you’re already in the podman ecosystem.
warmaster@lemmy.world 8 months ago
Ok that sounds intetesting, I’ve found Cockpit easier to use than Proxmox, I’m new to virtualization and I don’t want do nesting… I fear it will complicate things when I’ll need to do GPU passthrough.
How is Podman integrated into Cockpit?
Also, I had so much trouble trying to bridge my Home Assistant VM to my LAN. Are there any tutorials on how to do this from Cockpit?
SLaSZT@kbin.social 8 months ago
I just set it up last week, it works exceptionally well.
Did you also install podman-docker, make sure that the podman socket was running, and verify that the socket directory referenced in the config files was correct?
Those are the 3 things that I got a bit stuck on. In the end, I RTFM and all was well.