I dislike quadlets. Compose configs are way more concise, and just look nicer.

Podman is the RedHat implementation of the Open Container Initiative (OCI).

A Dockerfile and a Containerfile are both OCI. Docker and Podman can generally both use either.

Contrasted with Docker, Podman has better security defaults, and installers and licenses that are both actually open source. (Parts of Docker are open source. Parts are not.)

Docker used to lead with additional features beyond OCI such as Docker Compose, but Podman Compose has been a thing for a while, now.

The more mature a product is, the more likely it works perfectly with any OCI compliant tool.

For rookie work, I feel like there’s still fair odds the developer only uses Docker and may rely on some anti-pattern that requires setting “bad security=ok” settings before their project will work in Podman.

Your mileage may vary.

It’s a daemonless client for managing Linux containers. So any “docker” container. Most Linux distros have a native package for it too

not much man how about you

You’re that chain smoking black hat with a stack of computers, black out curtains several screens and not a single lightbulb.

Cult

Docker bypasses your firewall and runs as root. Only an idiot would allow that shit… I’m an idiot. But I’m fixing that.

Podman is unironically the better choice.

I like the idea of podman, but it’s just not stable. This meme was inspired by my frustration of trying to switch.

Just try to make docker comply with your firewall.

I literally did this yesterday and it wasn’t that hard. You just add iptables:False to the docker config file.

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.

Also, does Docker do rootless containers yet?

Wtf I thought docker was foss. Fml man

It also works better sooo

What exactly is your problem with Docker? It’s open source.

Also closed-source container images exist.

Docker is open source though. Docker desktop is not.

Also it’s more secure and performant as it’s rootless and daemonless.

I literally yesterday dealt with that. There’s an option to just turn off Docker’s firewall manipulation so you can do it manually.

I may be dumb but I apply the firewall at the router level (OPNsense). That should be fine, right?

Problem in chair, not in computer.

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

I’ve always had issue with podman-compose. So I setup a podman socket and use it with docker compose.

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.

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.

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.

Is your keyboard ok?

Also a solid technical reason for openSUSE

They look like a water type dugtrio.

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

There are still various incompatibilities between the two, and it becomes relevant if you need to work with any organization that has standardized on Docker-specific tooling.

Some containers don’t like non-root setups.

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