241–250 of 269 posts
Earlier quoted context omitted.
That's a you problem. Either use a rolling distro like Gentoo or Arch or learn to install software from source code yourself (it's not hard).
We both disagree with rsyring but I disagree with you even more! :D Installing from source code is hard! There's always some broken dependencies and these days I just cba. I'd sooner go complain on the internet than install a thing from the source code!
After Docker Desktop randomly started consuming insane amounts of memory again we switched to Podman and it was literally as easy as installing it and pointing it at our docker-compose.yml. Zero changes needed and now I don’t need to keep a daemon running. Great software.
don't forget `alias docker='podman'` for muscle memory
One thing I don't like about Podman is that it pretends to be docker-compatible while having some minor differences that will come to bite you. And users of your docker-based project who try to run it on Podman will come to you and complain.
My #1 complaint by far is that it --- pretty much silently --- depends on systemd to work correctly. Try having a docker-compose with a service that waits until a dependency is healthy --- in a host that has no systemd (such as Alpine Linux). The service will never start because Podman relies on systemd (and only systemd) to do the periodic healthchecks which it needs to do in order to handle such dependencies. And o…
Earlier quoted context omitted.
I’d wager it’s mainly just that deployment is mildly more annoying and requires more disparate steps. Especially if you want to go rootless (and you should). For someone that isn’t “Linux first” (like a baby developer learning to containerize their apps), the idea of dealing with systemd unit files or kublet configs, and having to created dedicated local service accounts (and remembering to enable linger) is somewhat…
It's not just mildly annoying, it completely ruins a great thing. Docker Compose is to stacks what Dockerfiles are to a single application. Podmans solution is to not commit to compose, but instead to create a bespoke mechanism involving a bunch of tiny files, all of which is insanely system (linux) specific, and therefore completely non-portable. I genuinely don't understand how someone can see the value of Docker,…
The better equivalent of docker compose is podman kube, which does use a single file. And it isn't bespoke, it uses the same format as kunernetes.
And if you prefer the docker compose format, podman-compose is available as a separate tool.
And FWIW docker compose is a separate tool from docker itself as well (and needs to be installed separately on several linux distros). And can actually work with podman instead of docker.
Anyone have experience switching from Docker to Podman? I have a lot of compose files in my homelab/automation setup and those are what I’m most concerned about.
Would be great to know if I can uninstall docker on Mac and just install https://github.com/containers/podman/releases and be good to go with my docker compose files ?! I have the feeling the docker company is communicating a lot with Apple because virtualisation got better and better over the years. I wonder if podman would be a speed downgrade here?
Doubtful. But for sure it would be a compatibility downgrade. When I tried podman-compose a couple years ago, I found it nowhere near usable, though I'm told it's improved since. If you want a better Docker for mac, you're looking for OrbStack.
Earlier quoted context omitted.
It's not just mildly annoying, it completely ruins a great thing. Docker Compose is to stacks what Dockerfiles are to a single application. Podmans solution is to not commit to compose, but instead to create a bespoke mechanism involving a bunch of tiny files, all of which is insanely system (linux) specific, and therefore completely non-portable. I genuinely don't understand how someone can see the value of Docker,…
Depends on your point of view. It can be argued that it’s Docker that is reinventing the wheel and doing its own bespoke process management, journal management etc when all of these are solved problems on Linux. Podman is instead reusing the platform which exists, Quadlets are just reusing systemd, so as a sysadmin I can manage, control and monitor docker containers using the same standard tooling that I already use…
It also would have only run on Linux hosts (and not all of those at that), so something else would have been adopted instead. Docker didn't win by being superior to every alternative, it won by being good enough and being everywhere. For portable orchestration, Desktop does ship with kubernetes that's literally one click to enable.
Earlier quoted context omitted.
I run Ubuntu 24.04 on my laptop and servers. The Podman version is 4.9.3. It may be incompressible to you, but I'm not alone in thinking it's a problem: https://github.com/podman-container-tools/podman/issues/2707...
You're running an LTS release first released in 2024. What exactly did you expect was going to happen?
Earlier quoted context omitted.
podman can work with kube files, which is the YAML format from Kubernetes. That's more "platform agnostic" than docker-compose. And it can be read as a documentation in the same way.
Kubernetes isn’t a great example of you can just read it like a document. The resource kind jargon is huge. Most compose files are small and use familiar linux jargon. I can give an non-dev IT person a compose file and they can understand every key. I can’t do that with K8s or Quadlet.
Earlier quoted context omitted.
> As long as they refuse to support installing on Ubuntu (and other popular distros), without relying on the distro repos which are always out of date, they will continue to lose to Docker. Your needs are incomprehensible to me: that is exactly why I use podman: a predictable version of it is in my distro's repos. I go to docker.com and how do I even install the thing? What's "docker sandboxes"? Get the latest versio…
I run Ubuntu 24.04 on my laptop and servers. The Podman version is 4.9.3. It may be incompressible to you, but I'm not alone in thinking it's a problem: https://github.com/podman-container-tools/podman/issues/2707...
One thing I don't like about Podman is that it pretends to be docker-compatible while having some minor differences that will come to bite you. And users of your docker-based project who try to run it on Podman will come to you and complain.
My #1 complaint by far is that it --- pretty much silently --- depends on systemd to work correctly. Try having a docker-compose with a service that waits until a dependency is healthy --- in a host that has no systemd (such as Alpine Linux). The service will never start because Podman relies on systemd (and only systemd) to do the periodic healthchecks which it needs to do in order to handle such dependencies. And o…
For anyone curious, there's more details on why this is tricky to do with Podman at https://github.com/podman-container-tools/podman/pull/27033 .