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.

I choose to use podman over docker because look at those cute seals 🥰

I choose Podman bc it's open source and that's kind of the reason for using everything as a container bc those are often also open source. Fuck docker

I use Podman (at work) because license fees.

It also can integrate with Systemd via Quadlets. Let's you control containers as a sytemd service. I personally use them for my home server and have been happy with it.

Mom, i can i have podman?

Mom: we have podman at home.

Podman at home: rootless docker

Also, does Docker do rootless containers yet?

It also works better sooo

Why would you use docker when you could use podman?

I use docker since it's what I learned on a decade ago, and my nas that I started from supports docker bit not podman in the 'app store'. I have three other machines running plain Debian, but I would want everything to work together, y'know? I've got a set-and-forget setup and I'd rather not break things without substantial benefit...

Plus everybody is like 'it's the same thing, no learning curve' but then I start reading up on it and uhoh, learning curves :p

It does, but it seems like it's still a bit of an afterthought. But it's getting better.

Still tho, podman is fine and I like the project as an alternative to docker.

Adding my voice: Podman is great

The learning curve for quadlets is quite harsh in my opinion. I started with podman compose 3 years ago for my homelab, because it allowed user containers.

I tried to migrate to quadlets unsuccessfully, several times over the years. it was only recently that my self-hosted Qwen was capable enough to figure out where I was messing up and automate the process a bit.

I probably wasn’t sufficiently motivated. It felt like podman compose is basically docker compose, but quadlets are a quite a bit different in form and function, so I was never able to grok them:

There is a tool named Podlet that can help translate to quadlets. I was able to fully translate my unraid and compose setups to quadlets.

Wtf I thought docker was foss. Fml man

Podman is a better choice.

Docker is foss. Docker desktop and docker sbx are not.

What's the benefit over Docker?

Not requiring a service running in root context.

Docker has the advantage of fucking working.
Every time I use podman, something is wrong. Especially with networking. I mean good luck running a compose file first time.
Nowadays I run both. I always gives podman a go first. Almost always end up on docker

Problem in chair, not in computer.

Isn't that only for docker desktop?

How does podman handle docker compose tasks?

Skill issue, as the youths call it these days.

There's podman-compose available through your package manager or pypi.

I still know it as Layer 8 issue.

You_guys_use_docker?.jpg

While I've never used it myself, Docker Rootless mode seems to also allow this?

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.

Plus everybody is like 'it's the same thing, no learning curve' but then I start reading up on it and uhoh, learning curves :p

Exactly this. I tried podman, as a "container" newb, based on the idea that it's a (better) drop-in replacement for docker, but it didn't work. My quick attempts to resolve it went nowhere, and there were no instructions for the container I was trying to spin up for podman to explain the differences required.

So, in frustration, I decided to try docker and it just worked.

Good enough for me, for now. I still prefer the idea of not having a daemon running with root privileges, so I'll likely move over to podman eventually, but I only have so much time to waste tinkering with my setup. And if it ain't broke, don't fix it.

I know it as PEBKAC, closer to @crypt0cler1c's. I like Layer 8, þo.

Through a hacky Python script (podman-compose), 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.

Rootless, better integrated with system, a bit faster and lighter on resources. Also it supports k8s style yaml configuration both ways and a lot of people are more familiar with them and they also provide some (minimal) interoperability.

podman quadlets are next level

Couldn't someone like you type up a short list with tips and tricks and post it where the newbies can find it?

Can you stop using thorn? It's quite a problem for some people, it makes reading very hard for them

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've always had issue with podman-compose. So I setup a podman socket and use it with docker compose.

10 years too late.

Use docker rootless.

Docker rootless has been more stable for me than podman

if you’re asking with regards to systemd orchestration, no.
i love deploying containers as Ansible -> systemd -> podman.

No, they mean the license costs. I'm pretty sure, you only have to pay a fee for Docker Desktop...

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.

We used to call it a carbon interface error.

It was also a 1-oh-4 when I was young.

It isn't that easy to setup. Podman just works

Why would you use podman when you could

#!/bin/ksh

daemon_execdir="/home/etebase/src"
daemon_logfile="/var/log/etebase"
daemon="/home/etebase/pyenv/bin/uvicorn"
daemon_flags="etebase_server.asgi:application --host 159.100.247.89 --port 8000"
daemon_user="_etebase"

. /etc/rc.d/rc.subr

rc_bg=YES
rc_reload=NO

pexp="/home/etebase/pyenv/bin/python3 ${daemon} ${daemon_flags}"

rc_start() {
        rc_exec ". ~/.profile; ${daemon} ${daemon_flags} >> ${daemon_logfile} 2>&1"
}

rc_cmd $1

Also a solid technical reason for openSUSE

a bit faster and lighter on resources.

Can't confirm. I have two VMs with an identical image (about 200 MB).

Docker: Pulling the image takes about 10 seconds and needs about 200 MB diskspace.

Podman: Pulling the image takes about 15 minutes and needs about 110 GB diskspace.

Docker: Commands like "docker ps", "docker stop" etc. run in a few seconds.

Podman: Commands like "podman ps", "podman stop" etc. take at least one minute.