docker-nginx VS podman-compose

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

Podman (via podman-compose),

Source code for the feature is here if you care to inspect it:

https://github.com/containers/podman-compose/blob/bce40c2db3...

Admittedly, I'm still on podman 4.3.1, but I dont' see any reason why this would stop working in later versions of podman.

Can someone link me to what Compose means in this context? Google takes me to https://github.com/containers/podman-compose but I just wanna make sure that's what they are talking about.

🛑 Docker Desktop is free for personal use but requires a paid subscription for enterprises. A free open source alternative is Podman and Podman Compose which uses the same core syntax as the Docker tools and can be used as a near drop-in replacement.

I’m dumb. When I wrote the article it was late. Docker-Compose really was a game changer.

Yea Podman compose exists. I’ll add a section about docker compose to it in an update.

https://github.com/containers/podman-compose

From googling this error I've come across a few different threads but I haven't gained any success. Firstly I found this github thread which doesn't reference my error but still seems related. I followed the "sudo podman-compose systemd --action create-unit" and "podman-compose systemd -a register -f myfile.yml" minus the -f flag as it wouldnt run with that. This indeed created a [email protected] file, but its created in the /etc/systemd/user directory rather than /etc/systemd/system which raises an issue as I'm having to run these two containers as root. I try registering the podman-compose@torrent but I'm told the service doesnt exist. Running it as user I'm told it failed to connect to bus: no medium found. So I basically reached a dead end there.

Have a look at Podman Compose

You can also use podman-compose for the orchestration https://github.com/containers/podman-compose