←back to thread

I ditched Docker for Podman

(codesmash.dev)
1101 points codesmash | 1 comments | 05 Sep 25 11:56 UTC | HN request time: 0.204s | 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 #
1. pvtmert ◴[05 Sep 25 21:42 UTC] No.45143983[source]▶
Both (K8s and Compose) are well defined schemas, hence the conversation is mere mapping via search & replace. Bunch of `sed` statements could do that, LLM is an overkill for the job.

Meanwhile, kompose.io exists, which is exactly what it does (but with Go templates as far as I can tell)