I’ll have to give it another try.

I should clarify that the issues I had were podman compose being able to run unaltered compose files that worked with docker compose, many of which were fairly complicated. It may have been adequate for simpler use cases back when I tried it.

In my experience podman compose is not a sufficient replacement.

Docker compose can be used with podman via the podman socket daemon. It’s very easy to get working. Give it a try.

Oops. Thanks for the correction.

I hadn’t heard of quadlets. I’ll have to give them a look.

We’ve completely transitioned from docker to podman where I work. The only pain point was podman compose being immature compared to docker compose, but turns out you can run docker compose with podman using the podman socket easily.

Im not sure the software center being half baked is even the real problem.

One of the nice things about Windows is that you dont need a central, curated, repository for software. You can google the thing you want and just download an msi/exe of the latest stable version and, 99.9% of the time, leading back to your first point, it will just work.

This is what prevented me from using podman, unfortunately. That and the setup for devcontainers in vscode wasnt exactly seamless.

Unfortunate since their windows support is great.