111–120 of 152 posts
Earlier quoted context omitted.
Incorrect, the use of a non-root daemon is essential for isolation and security.
Im fully on board with the idea that root daemons shouldnt be necessary I just dont want systemd to become a dependency for yet again something else it shouldnt be a dependency for.
Earlier quoted context omitted.
1) Podman is available in default debian repos. https://packages.debian.org/bookworm/podman 2) `podman run --entrypoint="" --rm -it debian:stable /bin/bash` in most instances you can just alias docker to podman and carry on. It uses OCI formatted images just like docker and uses the same registry infrastructure that docker uses.
Where does it pull the Debian image from? I would think the Docker infrastructure is financed by Docker Inc as a marketing tool for their paid services? Are they ok when other software utilizes it?
I can't speak to what Docker Inc. is okay with or not.
Earlier quoted context omitted.
Huh, that's another uninformed take. systemd is at it's core an app for running services, such as containers. You should read up on podman and systemd before making up more arguments.
The point is that RedHat went on a tirade for years telling everyone: "Docker bad, root! Podman good, no root! Docker bad, daemon! Podman good, no daemon!". And then here comes Quadlets and the systemd requirements. Irony at its finest! The reality is Podman is good software if you've locked yourself into a corner with Dan Walsh and RHEL. In that case, enjoy. For everyone else the OSS ecosystem that is Docker actuall…
But yeah I already use a distro with systemd (most folks do, I think), so for me, using Podman with systemd doesn't add a root daemon, it reuses an existing one (again, for most Linux distros/users).
Earlier quoted context omitted.
Docker Engine is Apache 2.0, is this not a good license? Docker has a rootless mode too.
When you say "Docker Engine" that suggests other parts of Docker are licensed differently (I haven't looked into it). I'd say you have to compare the whole ecosystem and not just a single component either way.
FWIW, Podman has an open source alternative to Docker Desktop as well.
Earlier quoted context omitted.
The point is that RedHat went on a tirade for years telling everyone: "Docker bad, root! Podman good, no root! Docker bad, daemon! Podman good, no daemon!". And then here comes Quadlets and the systemd requirements. Irony at its finest! The reality is Podman is good software if you've locked yourself into a corner with Dan Walsh and RHEL. In that case, enjoy. For everyone else the OSS ecosystem that is Docker actuall…
But...you don't need systemd or Quadlets to run Podman, it's just convenient. You can also use podman-compose (I personally don't, but a coworker does and it's reasonable). But yeah I already use a distro with systemd (most folks do, I think), so for me, using Podman with systemd doesn't add a root daemon, it reuses an existing one (again, for most Linux distros/users).
Today I can run docker rootless and in that case can leverage compose in the same manner. Is it the default? No, you've got me there.
SystemD runs as root. It's just ironic given all the hand waving over the years. And Docker, and all it's tooling, are so ubiquitous and well thought out that Podman and friends are literally a reimplementation which is the selling point.
I've used Podman. It's fine. But the arguments of the past aren't as sharp as they originally were. I believe Docker improved because of Podman, so there's that. But to discount the reality of the doublespeak by paid for representatives from RedHat/IBM is, again, ironic.
Earlier quoted context omitted.
Huh, that's another uninformed take. systemd is at it's core an app for running services, such as containers. You should read up on podman and systemd before making up more arguments.
The point is that RedHat went on a tirade for years telling everyone: "Docker bad, root! Podman good, no root! Docker bad, daemon! Podman good, no daemon!". And then here comes Quadlets and the systemd requirements. Irony at its finest! The reality is Podman is good software if you've locked yourself into a corner with Dan Walsh and RHEL. In that case, enjoy. For everyone else the OSS ecosystem that is Docker actuall…
Earlier quoted context omitted.
But...you don't need systemd or Quadlets to run Podman, it's just convenient. You can also use podman-compose (I personally don't, but a coworker does and it's reasonable). But yeah I already use a distro with systemd (most folks do, I think), so for me, using Podman with systemd doesn't add a root daemon, it reuses an existing one (again, for most Linux distros/users).
Exactly my point. Today I can run docker rootless and in that case can leverage compose in the same manner. Is it the default? No, you've got me there. SystemD runs as root. It's just ironic given all the hand waving over the years. And Docker, and all it's tooling, are so ubiquitous and well thought out that Podman and friends are literally a reimplementation which is the selling point. I've used Podman. It's fine.…
I would argue that Docker’s tooling is not well thought out, and that’s putting it mildly. I can name many things I do not like about is, and I struggle to find things I like about it’s tooling.
Podman copied it, which honestly makes me not love podman so much. Podman has quite poor documentation, and it doesn’t even seem to try to build actually good designs for tooling.
Earlier quoted context omitted.
The point is that RedHat went on a tirade for years telling everyone: "Docker bad, root! Podman good, no root! Docker bad, daemon! Podman good, no daemon!". And then here comes Quadlets and the systemd requirements. Irony at its finest! The reality is Podman is good software if you've locked yourself into a corner with Dan Walsh and RHEL. In that case, enjoy. For everyone else the OSS ecosystem that is Docker actuall…
But...you don't need systemd or Quadlets to run Podman, it's just convenient. You can also use podman-compose (I personally don't, but a coworker does and it's reasonable). But yeah I already use a distro with systemd (most folks do, I think), so for me, using Podman with systemd doesn't add a root daemon, it reuses an existing one (again, for most Linux distros/users).
When I bring this up online the answer is invariably "well use quadlets then" (i.e. systemd).
>systemd doesn't add a root daemon, it reuses an existing one
lol the same could be said of every docker container ive ever run....
Earlier quoted context omitted.
But...you don't need systemd or Quadlets to run Podman, it's just convenient. You can also use podman-compose (I personally don't, but a coworker does and it's reasonable). But yeah I already use a distro with systemd (most folks do, I think), so for me, using Podman with systemd doesn't add a root daemon, it reuses an existing one (again, for most Linux distros/users).
Exactly my point. Today I can run docker rootless and in that case can leverage compose in the same manner. Is it the default? No, you've got me there. SystemD runs as root. It's just ironic given all the hand waving over the years. And Docker, and all it's tooling, are so ubiquitous and well thought out that Podman and friends are literally a reimplementation which is the selling point. I've used Podman. It's fine.…
that means your podman containers dont run as root unless you want them to.
mine runs as user services
Earlier quoted context omitted.
Im fully on board with the idea that root daemons shouldnt be necessary I just dont want systemd to become a dependency for yet again something else it shouldnt be a dependency for.
Huh, that's another uninformed take. systemd is at it's core an app for running services, such as containers. You should read up on podman and systemd before making up more arguments.
Please try to understand the podman ecosystem before lashing out.