Open dominikzogg opened 4 years ago
I think you have to explain more of the wanted behaviour or you should take a look at multi-stage builds (https://docs.docker.com/develop/develop-images/multistage-build/#use-multi-stage-builds) what might already be what you maybe want?! What's the difference between your prod and dev container, just different config files or a complete different build result which can't be modified after the build is through? Why does the container contain stuff specific for dev/prod? Why not just build it, push the result to something like artifactory/gitlab and deploy it to prod/dev environment where again a container can be but moving/keeping enviromental stuff around in the image, isn't best practice (my understanding).
Wished behavior
I would love to have the possibility, to expand docker containers, for example extends a production ones for dev and add the additional dev stuff, without the need of build the prod container and then build the dev.
Which means Dockerfile (FROM) would be build first and used as a base image for the Dockerfile it gets referenced.