←back to thread

I ditched Docker for Podman

(codesmash.dev)
1101 points codesmash | 2 comments | 05 Sep 25 11:56 UTC | HN request time: 0s | source
Show context
tomrod ◴[05 Sep 25 12:12 UTC] No.45137625[source]▶
Most of my containers end up on k8s clusters as pods. What else would one use podman or docker for beyond local dev or maybe running a local containerized service?
replies(3): >>45137640 #>>45138052 #>>45138277 #
sc68cal ◴[05 Sep 25 13:02 UTC] No.45138052[source]▶
Someone has to manage your kubernetes environment. Depending on the nature of your workload, it may not be worth running kubernetes and instead just run everything via podman on your hosts. It really depends on how much investment you have in Kubernetes YAMLs.
replies(1): >>45138463 #
1. devjab ◴[05 Sep 25 13:41 UTC] No.45138463[source]▶
I suspect a lot of places pour them into Azure Kubernetes Services and Azure Container Apps for this exact reason. I assume other cloud provices have similar services.

Though as someone who's used a lot of Azure infrastructure as code with Bicep and also done the K8s YAML's I'm not sure which is more complicated at this point to be honest. I suspect that depends on your k8s setup of course.

replies(1): >>45183098 #
2. sc68cal ◴[09 Sep 25 15:15 UTC] No.45183098[source]▶
This is very true. My circumstances are a little unusual where using Azure costed more than running it internally on VMs, and running k8s or an equivalent didn't really add much value since I would have had to manage that, and my workload is uniform where each VM runs the same services so just running a podman pod was easier. There was no need for dynamic scheduling and scaling would just be launching more VMs and running more podman pods, and the entire deployment is just an Ansible playbook that preps the VM after boot then launches the containers. It didn't make sense to have another kind of YAML file to deploy the containers.