I use this trick to push to servers in an unnecessarily tight network I have to deploy to sometimes that can't see my source control / container registry.
But I do it for Docker. I have overall the sense that Podman is trying to accomplish feature parity with Docker but isn't there yet. Feedback on this formulation?
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).
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.