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
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
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.
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.
It also works better sooo
Also, does Docker do rootless containers yet?
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.
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
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.
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
Mom, i can i have podman?
Mom: we have podman at home.
Podman at home: rootless docker
Podman is a better choice.
What's the benefit over Docker?
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.
At work, avoiding surprise licensing fees. If you ever have over 250 employees or over 10 million revenue, you owe a subscription.
At the home, easy orchestration with systemd
I choose to use podman over docker because look at those cute seals π₯°
Docker became a license nest despite actual devs using k8s like a normal person should.
Meanwhile podman gave us rootless containers, CDI, and quadlets which far outweighs whatever docker is limping to the barn with.
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.
Podman is unironically the better choice. Just try to make docker comply with your firewall...
Docker bypasses your firewall and runs as root. Only an idiot would allow that shit.... I'm an idiot. But I'm fixing that.
I'm curious why you feel this way? I'm kinda the opposite β podman has features I use that Docker doesn't.
This is why I don't like Docker compared to Podman:

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 use Podman (at work) because license fees.
Adding my voice: Podman is great
podman is great.
Only gripe:
~ $ pomdan ps
No command pomdan found, did you mean:
...
I know, alias it, but man, I don't wanna.
I mean, that definitely seems like a you problem.
Pomdan won't work on my system because that is my alias to send Dan a message that I would like some more Pom.
Ngl after trying out Rootless Podman on my system (I was playing with Distrobox) I kinda wanna switch my whole Homelab to it, I'm just lazy, afraid the move to rootless with blow up everything and have zero fucking free time.
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
y'all use containers still? I run my site with native installed software configured by hand like a TRUE sysadmin!