Live data from Hacker News

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

redhat.com

31–40 of 89 posts

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

#31

Earlier quoted context omitted.

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

Its broken with alias but what's this about the podman-socket? Do you know where I can take a look at that?

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

#32

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 only dislike Podman because some distributions used it as an alias for docker which made a lot of docker-compatible software to not work on that distribution unless some workarounds. I wouldnt normally blame the application for this but in this case they are both, application and distribution, from the same dev.

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

#33

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 only dislike Podman because some distributions used it as an alias for docker which made a lot of docker-compatible software to not work on that distribution unless some workarounds. I wouldnt normally blame the application for this but in this case they are both, application and distribution, from the same dev.

Agreed, the `podman` command is 95% drop-in compatible with the `docker` command, but those edge cases are annoying and I would rather just use the docker cli backed with podman running the containers.

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

#34
post #23

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…

> docker-compose with a single env variable what is that env variable?

Probably DOCKER_HOST[0][1]

[0]: https://docs.docker.com/reference/cli/docker/#environment-va...

[1]: https://podman-desktop.io/docs/migrating-from-docker/using-t...

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

#35
post #23

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…

> docker-compose with a single env variable what is that env variable?

[deleted]

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

#36
post #30

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…

> It's also usable via docker-compose Is that "docker-compose" (with a dash) or "docker compose" (with a space)?

Both should do exacly the same, they are just installed differently. docker compose is installed as docker CLI plugin (Linux only), and docker-compose is installed as standalone binary.

See ref: https://docs.docker.com/compose/install/#scenario-two-instal...

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

#37

Earlier quoted context omitted.

I only dislike Podman because some distributions used it as an alias for docker which made a lot of docker-compatible software to not work on that distribution unless some workarounds. I wouldnt normally blame the application for this but in this case they are both, application and distribution, from the same dev.

Agreed, the `podman` command is 95% drop-in compatible with the `docker` command, but those edge cases are annoying and I would rather just use the docker cli backed with podman running the containers.

Podman has a docker frontend. On Fedora, it is packaged as podman-docker, I believe. I recently went through the pain of getting testcontainers working on Fedora 41 with Podman. After enabling the Podman socket and setting an environment variables, I was off to the races!

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

#38
post #30

Earlier quoted context omitted.

> It's also usable via docker-compose Is that "docker-compose" (with a dash) or "docker compose" (with a space)?

Both should do exacly the same, they are just installed differently. docker compose is installed as docker CLI plugin (Linux only), and docker-compose is installed as standalone binary. See ref: https://docs.docker.com/compose/install/#scenario-two-instal...

There are subtle differences between the two and not exactly the same.

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

#39

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 think you can use the VSCode Docker extension if you enable the Podman socket.

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

#40

Earlier quoted context omitted.

Both should do exacly the same, they are just installed differently. docker compose is installed as docker CLI plugin (Linux only), and docker-compose is installed as standalone binary. See ref: https://docs.docker.com/compose/install/#scenario-two-instal...

There are subtle differences between the two and not exactly the same.

That would be news to me, as both are pointing to the exact same GitHub repository[0]. Can you name the differences?

[0]: https://github.com/docker/compose

Post reply on HN