The current Docker installable containers use static environment settings for for example database server, ldap server, kafka server, etc. This means we need to create an image for every environment increasing the possibility to have different code bases for the environments.
It would be better to externalize the environmental settings and pass then when the container starts. So the image can be made once and be used through the complete DTAP street. You then have the option to run multiple T environments (which now means yet an other image to be build).
Build 1 image and create multiple environment files. Creating an extra environment file most likely takes less time as creating a new image.
|Who would benefit from this IDEA?||As a DEV engineer I only need to create 1 image instead of 1 per environment. As an OPS engineer I would like to run just 1 docker image for every environment so I don't need to take of the different images per environment.|
|Priority Justification||Best practice to have environment specific settings not inside the image; Faster delivering of images (just 1 instead of 1 per environment; faster testing).|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions