podman-nginx-socket-activation VS docker-nginx

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.

Add a brief sleep to the Nginx container's CMD. The default is CMD ["nginx", "-g", "daemon off;"], so something like command: ["sleep", "4", "&&", "nginx", "-g", "daemon off;"]. Didn't try this so not sure whether it'll work or not. Glancing at their docker-entrypoint.sh this will disable autoconfiguration from /docker-entrypoint.d/ (sigh).

A few time ago, I created the this post about nginx official image ENTRYPOINT "issue": https://github.com/nginxinc/docker-nginx/pull/752 .

An alternative to this approach, you could also write a template Dockerfile and then write some shell script that you would run locally to take that template and then write/generate Dockerfiles for each. Many of the official Docker images are setup and built this way. Here is an easy example of the nginx Docker image repository. https://github.com/nginxinc/docker-nginx It has three different templates in the root of the repository and has the update.sh script that is run to take those and write them out to a directory and essentially do a find and replace on the templates in the template. Those generated directories are then committed to the repository and pushed up to be built and published as Docker images.

It's a bit odd to use a custom docker image, rather than the one maintained by nginx Inc though:

https://github.com/signalapp/Signal-TLS-Proxy/blob/main/ngin...

Vs

https://github.com/nginxinc/docker-nginx

For one, this is 5 versions behind (1.18 vs 1.23).

In general seems caddy or haproxy might be a better fit - but nginx is a perfectly fine choice I suppose.

The container image docker.io/library/nginx will hopefully soon have support for socket activation. My PR got merged 9 days ago but the current image does not yet have the funcationality.

} ``` I have fixed the templates at https://github.com/nginxinc/docker-nginx/pull/533