3 ms·
I like this Podman feature: Support for socket activation Podman will pass on the socket-activated socket to the container. I wrote a small example demo for s
by eriksjolund 5y ago
I like this Podman feature:
Support for socket activation
Podman will pass on the socket-activated socket to the container.
I wrote a small example demo for setting up socket activation with systemd, Podman, and a MariaDB container:
https://github.com/eriksjolund/mariadb-podman-socket-activation https://github.com/eriksjolund/mariadb-podman-socket-activat...
- mikepurvis 5y agoOverall the integration story between podman and systemd is way, way better than with Docker. And that's in both directions, from using the host's systemd to start and manage containers, but also for running systemd within podman containers.
- freedomben 5y agoI would definitely expect that given the history of systemd and docker. IIRC difficulty Red Hat team had with integrating systemd and docker was one of the reasons why they started Podman rather than continuing to push everything upstream to docker. The docker team didn't want docker to have to accommodate systemd and refused some contributions that were important for a good integration.* *There's still some bad blood out there about it, so I just wanted to make explicit that I'm not making a value judgment on docker's refusal. I'm not educated enough on the details to make a fair judgment. Sometimes you have to say "no" to features to protect your product.
- nunez 5y agoOne of the folks that wrote THE manual on how to get systemd to work with Docker works at Red Hat on podman, so that's not surprising at all.