Anyone know a good resource for understanding the fundamentals of containers, in particular, how it persists state?
Also maybe how different products (kubernetes, podman, docker) fit into this space?
Thanks in advance!
Podman 4.2.0
71–80 of 104 posts
Re: Podman 4.2.0
#72Does anyone have experience “migrating” from docker to podman on a somewhat large scale? I am starting a new job soon in a DevOps role where the devs use both podman and docker and although the resulting images are the same, using two tools where one would suffice does not seem optimal. For context, it is a medium-sized (~40 devs) commodities trading company running some hundred applications in azure k8s but consider…
We got burned hard last year around GPUs (ai) and compose being not ready for enterprise settings for technical and redhat politics reasons, which are top use cases in the wild. Networking also looked problematic. We hadn't tried k8s for podman, which likely has its own issues.
So defaulting to docker would be the less risky bet and relegate podman to opt-in by trailblazers.
Podman core development is impressive, so frustrating to see the broader ecosystem issues.
Re: Podman 4.2.0
#73I like this Podman feature: Socket activation of containers Advantages: - Faster network. Rootless Podman will run with native network speed. Normally rootless Podman runs with reduced network speed due to the performance penalty that comes from using slirp4netns. - Improved security as you can disable the ability to establish outgoing connections with --network=none. The container can still communicate over the sock…
Podman 4 supports netavark which to my understanding should solve a lot of the networking issues with slirp4netns
Not for rootless containers unless there’s a development I’m unaware of.
Re: Podman 4.2.0
#74Anyone know a good resource for understanding the fundamentals of containers, in particular, how it persists state? Also maybe how different products (kubernetes, podman, docker) fit into this space? Thanks in advance!
Maybe articles like https://www.infoq.com/articles/build-a-container-golang/ could help? Basically learn how to build a simple one.
Re: Podman 4.2.0
#75I love Podman so much. It's seamless integration with systemd is a killer feature, as well as being able to generte Kubefiles. My main problem used to be feature parity with docker networking, but that seems to be mostly resolved since 4.0.
Trying to convince my team to use podman instead of docker (even though I've been using it myself primarily for months without issues), that's another story.
Re: Podman 4.2.0
#76I was looking at this just last night and the story with Ubuntu is horrible. That's essentially going to be stuck on v3.4 for ten years because it's "a lot of work" to get into that distribution. You'd think an entity the size of RedHat trying to take the reins from Docker would understand that this is an investment they have to make to make it a first-class replacement. I also installed it on Windows to see how the…
Red Hat has no official affiliation with Canonical who make Ubuntu. If you want to test podman you 'll have better luck using an OS from the Fedora ecosystem where Red Hat has affiliations and is actively contributing. Since you mentioned Windows I 'd suggest trying something like this [1] or this [2] [1]: https://github.com/yosukes-dev/FedoraWSL [2]: https://github.com/WhitewaterFoundry/Fedora-Remix-for-WSL Disclaim…
There's also Arch, or basically anything else besides Ubuntu. Podman isn't the only thing that is chronically out of date on it. Ubuntu has definitely lived long enough to become the villain.
Re: Podman 4.2.0
#77Earlier quoted context omitted.
Podman 4 supports netavark which to my understanding should solve a lot of the networking issues with slirp4netns
Not for rootless containers unless there’s a development I’m unaware of.
Yeah it works for rootless now too or at least that is my understanding.
Re: Podman 4.2.0
#78Now if Gitlab.com only supported leveraging Podman in their runners.
Podman is supported as a gitlab-runner now, as I understand it.
Re: Podman 4.2.0
#79Not a Podman or Docker-specific question/complaint, but is anyone working on a solution around UID/GID remapping between container and host? Not the "solution" offered by user namespaces, because those can only do a 1:1 remap, but an "anything any user writes inside the container is owned by the host user".
In other words, if host UID 1000 runs a container that has UID 100, 101, 102 and they all write files to a mounted volume, it would be great if all file writes were attributed to the host UID of 1000.
Instead, if user namespaces are configured correctly they would attribute to UID 1000, 1001, 1002 on host.
Re: Podman 4.2.0
#80Not a Podman or Docker-specific question/complaint, but is anyone working on a solution around UID/GID remapping between container and host? Not the "solution" offered by user namespaces, because those can only do a 1:1 remap, but an "anything any user writes inside the container is owned by the host user". In other words, if host UID 1000 runs a container that has UID 100, 101, 102 and they all write files to a moun…
fuse-overlay has some support for this, but it is fairly experimental. Basically it allows mapping of all files to a single UID, and then stores container owners/permission in XAttrs. When fuse-overlayfs exposes the image to the container process it exposes the xattr user/group and permissions.