←back to thread

I ditched Docker for Podman

(codesmash.dev)
1101 points codesmash | 2 comments | 05 Sep 25 11:56 UTC | HN request time: 0.461s | source
Show context
mrighele ◴[05 Sep 25 12:47 UTC] No.45137889[source]▶
> If your Docker Compose workflow is overly complex, just convert it to Kubernetes YAML. We all use Kubernetes these days, so why even bother about this?

I find that kubernetes yaml are a lot more complex than docker compose. And while I do, no, not everybody uses kubernetes.

replies(3): >>45138013 #>>45138269 #>>45143229 #
esseph ◴[05 Sep 25 13:00 UTC] No.45138013[source]▶
Having an LLM function as a translation layer from docker compose to k8s yaml works really well.

On another note, podman can generate k8s yaml for you, which is a nice touch and easy way to transition.

replies(4): >>45138153 #>>45138487 #>>45143983 #>>45146146 #
politelemon ◴[05 Sep 25 13:13 UTC] No.45138153[source]▶
Use an LLM is not a solution. It's effectively telling you to switch your brain off and hope nothing goes wrong in the future. In reality things do go wrong and any conversation should be done with a good understanding of the system involved.
replies(3): >>45138230 #>>45138349 #>>45142425 #
1. brennyb ◴[05 Sep 25 19:11 UTC] No.45142425[source]▶
"Using an IDE is not a solution" same arguments, same counter arguments. An abstraction being leaky does not mean it's useless. You will always need to drop down a layer occasionally, but there's value in not having to live on the lower layer all the time.
replies(1): >>45146115 #
2. lmm ◴[06 Sep 25 02:33 UTC] No.45146115[source]▶
The difference being that when your IDE makes a mistake you can understand and debug it, and maybe even patch it to fix it (or failing that at least understand what triggers it and work around it).