I am running my entire homelab from podman quadlets (systemd managed podman containers) and it’s honestly very dope. Podman gets a bad rap for being second tier to docker but they legit have a bunch of awesome features for Linux users specifically that make it way nicer. Using systemd for docker status can add some misdirection occasionally, but having the logs from containers directly in journalctl alongside the rest of my system logs is amazing

🤘

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

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

Not the poster, but I kinda get this sentiment. For my laptop and things that I do for work, I prefer Podman. Better security posture out of the box, and I’m typically crafting my own pods to work a specific way.

But, if I am just trying to start up some app/service and I’m following the GitHub documentation with the project…I want to just copy and paste and there isn’t a 1-for-1 for docker compose. Podman does have an alias package so you can say docker on the cli, but the “compose” part of it is not as good if I just want something to run without dicking with it.

So in short, if I’m making something with a container or want to have hands on control, I prefer Podman. If I’m running something “off the shelf”, like just running someone’s docker compose files files from their Github, I’m just running Docker man.

This! Podman rootless quadlets is so powerful and beautifully simple. Just look at that faaar superior security model and hos it doesnt even need a service to manage services because it just integrates natively with systemd I replaced my entire container layer from Rocker Swarm way back with K8s. Then it dawned on me I dont want the pods to move to another node by themselves anyway and then I just moved to Podman quadlets managed Ansible. Oh, and the podman pods are awesome as well.

It doesn’t and I’m sure there are benefits, but for basic home services daemonless translated directly into more work for no benefit.

What’s the benefit over Docker?

Pomdan won’t work on my system because that is my alias to send Dan a message that I would like some more Pom.

I mean, that definitely seems like a you problem.

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

Also closed-source container images exist.

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

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.

Wtf I thought docker was foss. Fml man

Docker is open source though. Docker desktop is not.

It also works better sooo

Also, does Docker do rootless containers yet?

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

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

It’s why I just ran portainer instead