Using CMD[...] breaks NGINX default entrypoint about runtime-env-cra HOT 3 OPEN

Hey!

Glad you figured it out. Can you explain a bit more in-depth why you would need to do that? I'm not sure I understood why you needed this.

from runtime-env-cra.

Sure thing,

basically I'm using templates for NGINX configuration (described here).

And one of the scripts inside NGINX's /docker-entrypoint.d, namely 20-envsubst-on-templates.sh is crucial to me, because it's responsible for moving /etc/nginx/templates/*.template files into the /etc/nginx/conf.d dir, while replacing placeholders inside with envsubst .

When I introduced your lib (which is awesome, btw), my usual pipelines and deployments stopped working. Basically my NGINX based containers would not have my custom configuration in place, but rather the default one which comes with the NGINX, and that happened because your example said to put a specific CMD [...] in Dockerfile, which is doing what it should, but it makes the NGINX /docker-entrypoint.sh skip all its job, including the above script.

from runtime-env-cra.

Ah, I see, okay. You have a very custom setup script then :)

Can you create some detailed instructions on how one can achieve this?

• How to create that custom Dockerfile
• Why you needed that

I'm happy to update the README for this use-case. I can also play around with it later to see what could be the best solution.

from runtime-env-cra.