Support dynamic loading of additional entrypoint scripts (entrypoint.d pattern)

[AaronMcHale]

Welcome!

• Yes, I've searched similar issues on GitHub and didn't find any.

What did you expect to see?

A common pattern across docker images is the /entrypoint.d directory, which allows for dynamically loading additional shell scripts during container start-up without having to replace the entrypoint script provided.

For example, the nginx image provides this support in their entrypoint script. Nginx's docker-entrypoint.sh script looks for the /docker-entrypoint.d directory, and if it contains any scripts, those will be executed. The nginx docker repository provides scripts which will be loaded by default.

In my specific case, one of the things I'd like to do on container start-up is to generate my own default TLS certificate on start-up, this would be easily done using a entrypoint script, and having support for /entrypoint.d (or /docker-entrypoint.d) would mean I don't have to override the entrypoint script provided.