Skip to content

Comment on Podman can transfer container images without a registryparent

Comments

Thanks for the update. Last I tried podman-compose was probably a year ago and it was clearly not ready.

So according to your update it's still not ready. Podman-compose is just a shell wrapper that translates compose yaml into podman shell commands. Which is why it will never really work imo because it's a hack.

We really need some OCI way of declaring containers. Recently apko[1] was announced but it's for apk systems so I'm not sure how it helps me on Fedora.

I think the idea was that you should be able to use the Kubernetes format spec to specify podman Pods. But I have yet to see that work. Until then podman is just something I use locally, but I still need docker to help my devs. There is no way I can force podman on them.

1. https://github.com/chainguard-dev/apko

Podman-compose is just a shell wrapper that translates compose yaml into podman shell commands. Which is why it will never really work imo because it's a hack.

Isn't Docker Compose the exact same thing though?

Well sort of, I mean it's some sort of python script so maybe it uses the docker py client instead of running docker commands with system. I dunno.

But my experience with podman-compose has been that it's not ready, mainly for more complex compose setups with different network access. I think that is what Pods are perfect for.

Compose has been rewritten in golang. I think it talks to the Daemon directly now.

Oic, nice. I still have the python module installed then I guess.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.