What took them so long?
Waiting for IBM to buy them? (half joking)
Or The Onion!
Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF
21–30 of 89 posts
Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF
#22Podman actually works really well. Out-of-the-box virtually-no-configuration-needed rootless containers. It's also usable via docker-compose with a single env variable. (podman-compose wasn't up to par for us) We've been using it for a couple of years running and managing hundreds of containers per server - no feeling of flakiness whatsoever. It's virtually zeroconf and even supports GPUs for those who need it. It's…
The IO through fuse-overlay is performance limiting though. It's almost half the speed as overlay directly for layers with many tiny files.
Note that Linux allows you to mount overlay within a user namespace if you are root within the user namespace.
In other words, if you are root within a container; even though it is not root on the host; Linux accepte ton mount overlay filesystems (most filesystems are not allowed). `man user_namespace`
Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF
#23Podman actually works really well. Out-of-the-box virtually-no-configuration-needed rootless containers. It's also usable via docker-compose with a single env variable. (podman-compose wasn't up to par for us) We've been using it for a couple of years running and managing hundreds of containers per server - no feeling of flakiness whatsoever. It's virtually zeroconf and even supports GPUs for those who need it. It's…
> docker-compose with a single env variable
what is that env variable?
Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF
#24Does podman support docker compose files well? Devs love them for local environments.
Yes it doesm even with rootless. We are using it in prod.
Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF
#25Reading about Keycloak and how long it is taking to patch critical vulnerabilities, I wonder is CNCF becoming how Apache was - where abandoned open source software goes to die.
Hopefully the Keycloak thing will spur more competition. I looked at some alternatives and settled on Keycloak because it was "obviously" the mature and hardened solution.
Well, clearly not.
Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF
#26To all those interested in podman, this book by Daniel Walsh is a gem. Highly recommended and it is free.
Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF
#27Podman actually works really well. Out-of-the-box virtually-no-configuration-needed rootless containers. It's also usable via docker-compose with a single env variable. (podman-compose wasn't up to par for us) We've been using it for a couple of years running and managing hundreds of containers per server - no feeling of flakiness whatsoever. It's virtually zeroconf and even supports GPUs for those who need it. It's…
If podman compose would parse env var strings correctly, then it would be on par. Not sure why that hasn’t been fixed but probably because it’s a stepping stone instead of a well thought out replacement.
Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF
#28Is CNCF new Apache foundation? Looks like everyone dumps their stuff there. Does not look promising. Am I missing something? Probably RedHat paid salary to podman developers, but who will pay salary to them now?
Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF
#29Is CNCF new Apache foundation? Looks like everyone dumps their stuff there. Does not look promising. Am I missing something? Probably RedHat paid salary to podman developers, but who will pay salary to them now?
Strimzi is CNCF, Strimzi still has a full time team of devs in RH.
Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF
#30Podman actually works really well. Out-of-the-box virtually-no-configuration-needed rootless containers. It's also usable via docker-compose with a single env variable. (podman-compose wasn't up to par for us) We've been using it for a couple of years running and managing hundreds of containers per server - no feeling of flakiness whatsoever. It's virtually zeroconf and even supports GPUs for those who need it. It's…
> It's also usable via docker-compose
Is that "docker-compose" (with a dash) or "docker compose" (with a space)?