I feel like this is such a common pattern at this point that there should be a much clearer go-to solution than there is. OCI containers are the lingua franca of software distribution now – why does it seem like the only option for deploying them that claims to be “production ready” is Kubernetes? I’m currently responsible for one environment that uses Docker Compose to do this, but it has some sharp edges and I’ve read enough horror stories to believe it’s not a clear winner. Also unless I’m mistaken, I’m pretty sure that Docker itself recommends against this. Also there’s the infamous (and deeply frustrating) iptables problem. I’m very aware of Podman, and though I’ve read much of the documentation and toyed with it a bit, I’ve not used it in production. When I investigated a year ago it seemed like everything was about deploying things with Kubernetes manifests. Now it seems like most new reference guides are about using Podman with Kubernetes. People who are architecting your production environment with containers on a VM: how are you doing it and is it exceedingly boring? Please share the love if so.

  • @vrutkovs
    link
    English
    15 days ago

    Podman and systemd. The drawback in comparison to Kubernetes is that it’s not trivial to maintain availability - you’d need to design smth like Deployments and ReplicaSets manually if its important