Live data from Hacker News

Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

redhat.com

11–20 of 89 posts

Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

#11
post #5

Does podman support docker compose files well? Devs love them for local environments.

I use podman with docker-compose files for my day-to-day work; spinning up databases and other service dependencies for locally running or containerized webapps.

podman-compose never worked very well for me, so I'm running with the podman.socket systemd service and the standalone version of docker-compose. That is however working flawlessly.

What I really like about podman (and which to be fair docker might have since catched up on) is that rootless containers work so well. Gone are the days where bind-mounting a project folder into a container would mess with your file permissions.

In my experience podman also feels easier and less invasive to install, although I can't say if the latter is really the case.

Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

#12

Reading 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.

I think that CNCF has better handle on abandonware, plus really good observably. https://devstats.cncf.io/

Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

#13
post #9
post #5

Does podman support docker compose files well? Devs love them for local environments.

I’ve been using it on my Fedora server because I make myself. I think all functionality and syntax is covered. However, the user feedback and TUI of docker-compose is way nicer (interactive at least). Also, podman compose does seem to recreate containers that do not need to be recreated in more cases than I have noticed docker compose do.

You can run the standalone version for docker-compose against podman. You just need to have the podman.socket systemd service running.

Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

#14
post #5

Does podman support docker compose files well? Devs love them for local environments.

Try podman kube generate and podman kube play. Podman can generate a Kubernetes YAML, and then you can run it with kube play.

I use it together with systemd in my home lab. It's Kubernetes for single node and without the bloat. I love it!

https://www.redhat.com/en/blog/kubernetes-workloads-podman-s...

Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

#15
post #5

Does podman support docker compose files well? Devs love them for local environments.

I use podman with docker-compose files for my day-to-day work; spinning up databases and other service dependencies for locally running or containerized webapps. podman-compose never worked very well for me, so I'm running with the podman.socket systemd service and the standalone version of docker-compose. That is however working flawlessly. What I really like about podman (and which to be fair docker might have sinc…

My only problems with Podman is the lack of up to date repos across systems, the fact that the latest raw binaries are managed by a maintainer out of the goodness of their heart, and that the VS Code extension ecosystem for managing pods is not integratable with the existing Docker stuff (and the replacement extensions are woefully underdeveloped).

Otherwise it honestly is great and preferable over Docker.

Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

#16
post #10

Earlier quoted context omitted.

That's my take as well. Red Hat's design choices fit into Linux much more neatly. Docker has always been rubbish with late cgroups v2 support, punching holes in my firewall, no rootless, etc.

> punching holes in my firewall I teach various Linux training courses. One of which is Containers. It always shocks several people per-class how Docker just blatantly ignores and rewrites existing firewall rules. And there's no real option to prevent that unless you want to manually configure ALL network routing. For me personally, that was one of the big issues the pushed me over to Podman. Also, Docker's insistenc…

I want to switch to podman. What are the general gotchas and difficulties you could see in doing that for multi architecture+os builds/deployments?

Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

#17
Podman 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 like docker but better, IMO.

Hope it gets a popularity boost from CNCF. Rooting for it.

Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

#18

Earlier quoted context omitted.

I use podman with docker-compose files for my day-to-day work; spinning up databases and other service dependencies for locally running or containerized webapps. podman-compose never worked very well for me, so I'm running with the podman.socket systemd service and the standalone version of docker-compose. That is however working flawlessly. What I really like about podman (and which to be fair docker might have sinc…

My only problems with Podman is the lack of up to date repos across systems, the fact that the latest raw binaries are managed by a maintainer out of the goodness of their heart, and that the VS Code extension ecosystem for managing pods is not integratable with the existing Docker stuff (and the replacement extensions are woefully underdeveloped). Otherwise it honestly is great and preferable over Docker.

I won't deny that the outdated repos was a pain in the past, but ever since ubuntu got to version 4 it's been working flawlessly for me.

I think version 4 was where podman became a reliable tool, whereas I found it to be flaky and unreliable in previous versions.

I don't use vs code extensions for managing my containers, so I can't say much about those, but I wonder if many of them won't work fine with an alias for docker and maybe the podman-socket running.

Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

#19
post #5

Does podman support docker compose files well? Devs love them for local environments.

For more information on compose files take a look at the Compose Spec [0], looks like podman compose supports the Compose Spec which Docker compose files use as well.

[0] https://github.com/compose-spec/compose-spec?tab=readme-ov-f...

Re: Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

#20

Podman 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…

I completely agree and have had the same experience as you with docker-compose working better than the alternatives.

Past versions of podman were flaky, but since version 4, which is now a couple of years old, I haven't had any issues whatsoever. I'd recommend anyone using containers on linux to try it out instead of installing docker out of habit.

Post reply on HN