There's a few places where Podman probably has to catch up with docker but conversely, I think Docker is still trying to catch up with Podman in regards to running rootless (i.e. running containers using a user account without having root privileges).
Does Podman have enough parity that I can run our Compose stack locally? Last I tried (months ago), enough things failed that I gave up, but it would be great if developers could easily develop locally without root (which causes a bunch of permissions problems).
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.
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.
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.
Yes Podman supports the Docker API and supports docker-compose directly a opposed to podman-compose which uses podman commands directly by reading the compose format and generating podman commands.
docker-compose2 has a bug with Podman right now, but a fix went into upstream this week to fix support.
Yes, having to set up the docker group is quite painful, and especially the membership requirement can cause issues when the account has to log in to the machine to be eligible for membership.
Comments
There's a few places where Podman probably has to catch up with docker but conversely, I think Docker is still trying to catch up with Podman in regards to running rootless (i.e. running containers using a user account without having root privileges).
Does Podman have enough parity that I can run our Compose stack locally? Last I tried (months ago), enough things failed that I gave up, but it would be great if developers could easily develop locally without root (which causes a bunch of permissions problems).
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
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.
Yes Podman supports the Docker API and supports docker-compose directly a opposed to podman-compose which uses podman commands directly by reading the compose format and generating podman commands.
docker-compose2 has a bug with Podman right now, but a fix went into upstream this week to fix support.
Yes, having to set up the docker group is quite painful, and especially the membership requirement can cause issues when the account has to log in to the machine to be eligible for membership.
Podman works with docker-compose in rootless mode, no need to set up the security questionable DOCKER Group.
Oftentimes exec newgrp docker can help. Of course fixes it only for that particular process.