Live data from Hacker News

Podman: A Daemonless Container Engine

podman.io

11–20 of 250 posts

Re: Podman: A Daemonless Container Engine

#15
post #7

I still miss an easy way to setup multiple containers in a single network like with docker-compose. podman-compose is not really useable.

You can use docker-compose with podman.

Through it has similar drawbacks as using docker-compose with docker.

As far as I know there is currently no rootless way on Linux to setup custom internal networks like docker compose does (hence why podman-compose doesn't support such things).

Re: Podman: A Daemonless Container Engine

#17
post #11
post #2

Anyone have experience with this? I love the idea of it being daemonless.

I’m a GPU driver dev and you guys are talking ~alien~, right now. What does “daemonless” mean? Why is that good?

In Docker each container process is a child of the Docker daemon process. If you need to apply security patches to the Docker daemon it kills all your running containers.

Re: Podman: A Daemonless Container Engine

#19
What's the status on ease of running on Mac? I know last time I seriously considered testing it out in my workflow, it was kind of crazy that I had to have a separate machine (VM or real) just to run container images...

I see in the docs [1]:

"Podman is a tool for running Linux containers. You can do this from a MacOS desktop as long as you have access to a linux box either running inside of a VM on the host, or available via the network. You need to install the remote client and then setup ssh connection information."

And yes, I know that Docker (and any other Linux container-based tool) also runs a VM—but it sets it up almost 100% transparently for me. I install docker, I run `docker run` and I have a container running.

[1] https://podman.io/getting-started/installation#macos

Re: Podman: A Daemonless Container Engine

#20
post #11

Earlier quoted context omitted.

I’m a GPU driver dev and you guys are talking ~alien~, right now. What does “daemonless” mean? Why is that good?

In Docker each container process is a child of the Docker daemon process. If you need to apply security patches to the Docker daemon it kills all your running containers.

Technically the parent process for a contained process with Docker is containerd-shim.

Also, Docker does support live restore if you want to keep containers running over daemon restarts https://docs.docker.com/config/containers/live-restore/

Post reply on HN