i genuinely run all my shit bare metal
🤘
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 had the same issue, but I just added my plain iptables rules to the DOCKER-USER table, which worked fine
Please elaborate…
Basically put:
{ iptables: False, Ip6tables: False }In /etc/docker/daemon.json
All my homies use nerdctl anyway.
Atleast Podman is faster + does not require a centralised daemon
It doesn’t and I’m sure there are benefits, but for basic home services daemonless translated directly into more work for no benefit.
Security is always a benefit 😎
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.
Container manager in Synology. Why?
It’s why I just ran portainer instead
docker/podman sucks, u can’t avoid using journald for logging. U also can’t avoid using overlayfs. Plain LXC is what I have at home
Switching colleagues over to Pdman desktop, whenever legal asks about licenses for DD. :)
Podman has some thngs rhat I don’t like but it ften works much better, and a lot f really great tools use it natively (like distrobox)
Is your keyboard ok?
podman is great.
Only gripe:
~ $ pomdan ps No command pomdan found, did you mean: ...I know, alias it, but man, I don’t wanna.
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’s podman?
not much man how about you
It’s a daemonless client for managing Linux containers. So any “docker” container. Most Linux distros have a native package for it too
Am I the only one who struggles with podman permissions? Every time I try to use it one service or another doesn’t work.
I tried for immich (only service I expose) and failed.
Linkwarden would not run without root.
I just use rootless docker, it’s way less hassle.
God I hate arguing with podman. Something doesn’t work and I can’t tell if it’s my quadlet or the app
I just use the native docker apps that truenas has preconfigured. The one time I needed a custom compose container I just bashed my face against the keyboard until it worked. This is how I feel about all containerization. There really should be an easier system. Nothing wrong with higher accessibility.
Podman is a better choice.
This meme taught me a lot with all these comments. Thank you
Why would you use docker when you could use podman?
Some containers don’t like non-root setups.
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 $1Oh why you gotta talk so dirty to this little chatbot
Did you mean rc_start $1 as the last line of that script?
Idk, I was lazy and copied from here instead of going to one of my actual OpenBSD installations and checking. Could be different on other BSD style inits.
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.
In almost all cases podman will work as a drop-in replacement. Problems usually arise from podman not being rootful by default, which does make a difference in most scenarios that involve volume mounts, exposing ports or other kinds of host resource access. You can run podman as root and nowadays even docker as rootless (though at that point you might be better off with podman).
Use docker rootless.
same, docker just works when I’m trying to use version pinning on half my containers so they don’t try using the wrong rocm version
