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.
podman is great.
Only gripe:
~ $ pomdan ps No command pomdan found, did you mean: ...I know, alias it, but man, I don’t wanna.
You_guys_use_docker?.jpg
podman quadlets are next level
I dislike quadlets. Compose configs are way more concise, and just look nicer.
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.
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.
Company confirmed that it is lighter and faster with multiple benchmark at the time of migration. Your case sounds like extreme misconfiguration.
Not requiring a service running in root context.
While I’ve never used it myself, Docker Rootless mode seems to also allow this?
It isn’t that easy to setup. Podman just works
10 years too late.
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
Isn’t that only for docker desktop?
It is! If you want to reduce exposure to this you really have to make sure mdm disallows installing it. The numbers trigger regardless of seats, and then you’re on the hook for the licenses for every employee using it.
So even if as a matter of policy you don’t use docker desktop, it’s possible engineers still do.
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…
my bad
Why would you use docker when you could use podman?
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 $1I 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.
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
Use docker rootless.
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
Docker is open source though. Docker desktop is not.
So, the Docker engine is free, just not the software under certain stipulations. See I don’t like that. A weird caveat for using it.
Wtf I thought docker was foss. Fml man
If you install the GUI it literally won’t let you open it unless you agree to their telemetry…
Docker is foss. Docker desktop and docker sbx are not.
Are you sure about that? I see Copyright at the bottom (maybe the name) and is free only for personal tier, everything else costs money. Maybe some of the containers are open source per https://www.docker.com/products/trusted-content/open-source/ but I don’t see where it says anywhere that the actual software that is docker is OSS let alone FOSS.
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.
Docker rootless has been more stable for me than podman
Mom, i can i have podman?
Mom: we have podman at home.
Podman at home: rootless docker
I choose to use podman over docker because look at those cute seals 🥰
Also a solid technical reason for openSUSE
Adding my voice: Podman is great
How does podman handle docker compose tasks?
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.
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.
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.
Couldn’t someone like you type up a short list with tips and tricks and post it where the newbies can find it?
I’ve always had issue with
podman-compose. So I setup a podman socket and use it with docker compose.There’s
podman-composeavailable through your package manager or pypi.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.
Can you stop using thorn? It’s quite a problem for some people, it makes reading very hard for them
I use Podman (at work) because license fees.
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.
Skill issue, as the youths call it these days.
I still know it as Layer 8 issue.
I know it as PEBKAC, closer to @crypt0cler1c’s. I like Layer 8, þo.
We used to call it a carbon interface error.
It was also a 1-oh-4 when I was young.
