Hacker News Reader

Comment by nikisweeting | Hacker News Reader

It should natively support running docker-compose.yml configs, essentially treating them like swarm configurations and "automagically" deploying them with sane defaults for storage and network. Right now the gap between compose and full-blown k8s is too big.

View on HN

So, what I'm hearing is that it should tie itself to a commercial company, who now have a private equity master to answer to, versus an open source technology run by a foundation

Besides, easily half of this thread is whining about helm for which docker-compose has no answer whatsoever. There is no $(docker compose run oci://example.com/awesome --version 1.2.3 --set-string root-user=admin)

docker-compose -f $(curl example.com/v1.2.3/awesome-compose.yaml)

helm is an anti pattern, nobody should touch it with a 10 foot pole

What? I didn't say any of that, OCI and docker-compose are both open formats, do it with podman for all I care.

> Right now the gap between compose and full-blown k8s is too big.

It's Hashicorp so you have to be weary, but Nomad fills this niche

https://developer.hashicorp.com/nomad

I really want to love nomad but I've never been able to get it working well for my workloads. I'm not a big fan of HCL, I really just want docker-compose++.

The compose-to-k8s mapping is deceptively complex due to fundamental differences in networking models, volume handling, and lifecycle management - tools like Kompose exist but struggle with advanced compose features.

Replace docker with podman and you can go the other way around, run a pod manifest locally.

Reply on news.ycombinator.com