Comment on Hey selfhosters, what are you selfhosting?
PriorProject@lemmy.world 1 year ago
Initially I was using rocky+podman but inevitably hit something I wanted to run that just straight up needed docker and was too much effort to try and get working. 🤷
Can you clarify some of the things you got stuck on with podman? I currently have a docker-compose based setup that I’m pretty happy with, but am rebuilding and am planning to experiment with podman play with k8s-style manifests as an alternative to compose. It’s still not clear to me whether podman is going to simplify my life or make it worse compared to docker and compose, and I’m curious about your insights and why you backed off from that architecture.
ratz@chatsubo.hiteklolife.net 1 year ago
Basically I ran into issues with building images from newer and more complex compose files that podman-compose just couldn’t pull apart.
Docker is still the go-to if you want shit to ‘just work’, it has an easier user experience, it’s what the vast majority of developers building containers are using. You can run rootless if you want without too much pain.
It has come a long way but the probability that you’ll run into some random edge case or other issue with podman is higher, podman-compose has some thorns (high likelihood you’ll need to hack on compose files), if you want containers to start without your interaction you have to bake up systemd unit files for them, etc. I’ve not messed with
podman-kube-play- wasn’t even aware of it, so can’t really comment as to how well that works.There’s nothing to lose by giving it a go except your sanity and time. 😁
PriorProject@lemmy.world 1 year ago
Thanks for the insights. I’ll see how it goes.