News for hackers. Stuff that matters.

A comment on Podman Desktop 1.6 released: Even more Kubernetes and Containers features. Parent comment

Re:Podman Desktop 1.6 released: Even more Kubernetes and Con... by R0flcopt3r on Wednesday December 20, 2023 @10:48AM (#38709950)
podman can't replace docker-compose. it can only replace docker. if you install podman-docker any docker command you run will be translated to a podman command. I think that should work when you run docker-compose as well.
[ Parent | on HN ]
Re:Podman Desktop 1.6 released: Even more Kubernetes and Con... by heffer on Wednesday December 20, 2023 @10:58AM (#38710068)
podman works great with docker-compose through the docker socket emulation. I just use the upstream vanilla docker-compose with it (also works with docker compose as a plugin for Docker CLI).

Podman Desktop also offers to set the socket emulation and Docker compatibility up for you, if you like.

[ Parent | on HN ]
Re:Podman Desktop 1.6 released: Even more Kubernetes and Con... by pydry on Wednesday December 20, 2023 @10:51AM (#38709984)
It's not quite enough. You also have to run a server too - docker-compose won't run without a docker service running.

podman-compose will and it behaves more or less the same way but it's quite a neglected piece of software - lots of bugs, lots of open PRs.

A lot of people talk about quadlets or k8s as alternatives but I don't think these are generally good substitutes for compose.

[ Parent | on HN ]
Re:Podman Desktop 1.6 released: Even more Kubernetes and Con... by asmor on Wednesday December 20, 2023 @01:21PM (#38711829)
If your distro is relatively recent, enable podman.socket (available as system and user unit) and things should just work as they do with docker. You may have to set CONTAINER_HOST though, and the new Docker CLI has the concept of contexts where you need to point the CLI at the right socket, but confusingly using docker as a library does not automatically add contexts as functionality, so Tools like flyctl (from fly.io) and melange (chainguard's APK builder) may still need CONTAINER_HOST anyway...
[ Parent | on HN ]
Re:Podman Desktop 1.6 released: Even more Kubernetes and Con... by pydry on Wednesday December 20, 2023 @04:41PM (#38713995)
at some point it's easier to just use docker
[ Parent | on HN ]
Re:Podman Desktop 1.6 released: Even more Kubernetes and Con... by asmor on Thursday December 21, 2023 @01:52PM (#38724971)
other tools prefering to use CONTAINER_HOST instead of docker contexts happens without podman too, because docker didn't build contexts into their go client library and it's instead all in the docker CLI.
[ Parent | on HN ]
Re:Podman Desktop 1.6 released: Even more Kubernetes and Con... by CoolCold on Sunday December 24, 2023 @09:53AM (#38753794)
can you please clarify, from technical perspective

> enable podman.socket (available as system and user unit)

Won't it make podman be daemon then if it'd be activated by socket?

Won't such a daemon be run as root then to be able to handle creation of networks/ports forwardings/multiple-users?

[ Parent | on HN ]
Re:Podman Desktop 1.6 released: Even more Kubernetes and Con... by asmor on Monday January 01, 2024 @09:37AM (#38832064)
As I said, there's a user unit (systemctl --user status podman.socket) that will run rootless just like using the podman CLI without elevation.
[ Parent | on HN ]
Re:Podman Desktop 1.6 released: Even more Kubernetes and Con... by mikae1 on Thursday December 21, 2023 @03:09AM (#38718126)
> podman can't replace docker-compose.

podman-compose[1] replaces docker-compose.

[1] https://docs.podman.io/en/latest/markdown/podman-compose.1.h...

[ Parent | on HN ]