Deployment with Docker

Generating the credentials at runtime

Unlike the database problem, this particular issue is not as easy to deal with, mostly because credentials are a tough problem to deal with from a security perspective. If you include a build argument or a baked-in environment variable, anyone with access to the image can read it. Also, if you pass in the credentials through an environment variable during container creation, anyone that has docker CLI access can read it so you're mostly left with mounting of volumes with credentials to the container.

There are a few other ways of passing credentials securely, though they are a bit outside of the scope of this exercise such as env variables that contain hashed passwords, using a broker secrets-sharing ...