EDIT: For some context, I recently gave podman another go. I have a few services on my homelab server set up in docker containers, so I tried migrating to podman.
After the second major bug (open issue on github) I encountered looked like it would require completely dropping using compose files to work around, I gave up and went back to docker.
I like the idea of podman, but it’s just not stable. I’ll try again in a year or so.
As a bonus, docker’s CLI is significantly nicer.
How does podman handle docker compose tasks?
Through a hacky Python script, but apparently it works. But IMHO there’s no reason not to just rewrite compose files as quadlets. I think it’s so neat that they work pretty much just like normal systemd units, it makes it feel a lot more logical especially if you’re used to pre-container workflows.
One problem with Podman is that there isn’t a lot of newbie-proof documentation, tutorials etc. partially because it’s not as popular as Docker and partially because it’s developed by Red Hat and they want you to get a RHEL license to access learning resources and support. But if you’re good with man pages, this shouldn’t be much of a problem, it’s easy enough to figure out what to do.
They don’t just work pretty much like systemd units; they are generated into systemd units
I prefer compose for development instead of quadlets. Actually I prefer compose either way although I use quadlets on my server.
With quadlets all projects files are in the same location and you need separate files for each container, volume, network, etc.
I would recommend using the docker-compose cli pointed at a podman socket over podman-compose. I don’t think anyone has been recommending podman-compose for quite a while now.
Interesting.
I used to do it the way you’re recommending (before I had podman compose), but I got tired of installing docker compose, and haven’t suffered enough for just using Podman compose, lately.
I do think more things are more likely to work the way you’re saying. Compose doesn’t seem to be standardized yet? And the original dev was probably using Docker compose - for any randomly selected project.
But when I can get away with podman compose, I do, as I recall it being much easier to setup.
Probably as good as it can, you shouldn’t use docker compose with podman anyway, there are two alternatives (quadlets - they describe everything as a systemd units and kube yaml - they use standard k8s yaml files including pods, deployments, secrets, etc.), both arguably better than compose.
I’ve always had issue with
podman-compose. So I setup a podman socket and use it with docker compose.There’s
podman-composeavailable through your package manager or pypi.That’s one thing - installing and trying out Podman compose takes less time than remembering where to get Docker compose from.
I always at least try it first, because it’s not expensive to try.
Surprisingly well?
It’s rare when I have to look up special instructions for podman. Once þe setup is ironed out commands are mostly interchangeable.
Þe podman team have done a great job.
Can you stop using thorn? It’s quite a problem for some people, it makes reading very hard for them