podman-nginx-socket-activation VS podman

https://github.com/eriksjolund/podman-nginx-socket-activatio...

I wrote an nginx socket activation example https://github.com/eriksjolund/podman-nginx-socket-activation (The example does not show nginx working as HTTP reverse proxy but I think tried that out before and it worked)

(I wrote a demo: https://github.com/eriksjolund/podman-nginx-socket-activation)

The difference is that with Podman its possible to create a systemd socket unit for the service (for example nginx.socket).

The problem when running rootless Podman with socket activation and docker.io/library/nginx is caused by the closing of file descriptor 3 in /entrypoint.sh.

You are correct. And there is an Ansible role for automated management: https://github.com/linux-system-roles/podman/

My opinion, yes, and RHEL are sure aiming for that. Whether they will succeed and whether it's better than Docker/ Kubernetes is down to personal opinion at least for now. Podman is trying to make it easy to work with it and to scale - there's an Ansible role under development. At the end of the day, Podman is made to be compatible with both Docker and Kubernetes syntax and general way of work, so I think if you know it well it shouldn't be too hard to learn the other technologies if needed.