I'd also like to reply to the other half of your comment: > Can you imagine the code that loads a configuration file directly into the code and the ops team un

I'd also like to reply to the other half of your comment: > Can you imagine the code that loads a configuration file directly into the code and the ops team unable to reconfigure things? Yes! That's what code is, actually! Code is stuff you put in a file which can't be configured easily, but is thus consistent between all deployments of the software. It often actually makes it easier for a problem to be found and reproduced if configuration is baked into the binary vs varying based on the environment the code is run in. In a way, docker images are a means of statically compiling a bunch of random stuff (like /etc/passwd) into your application at build time to remove more environmental variables. Really, loading a configuration file into the binary statically at build time isn't much different from having `const SOME_VARIABLE = "some value"` in your source code... the only difference is how you, the programmer, chose to represent that constant. The line between "configuration" and "code constants" is very thin, so I don't think what you say is a sensible criticism.