In one scenario, when my IT team deploys many applications through docker. We have our own images of dockers, and others from the Internet registry.
One (base) image can be an Operating System image , and the other can be a runtime (for java, ruby, etc.) and still some other special tools (for example, git, some libs) can be different . Then, finally, we have images of our applications .
This means that our container hierarchy looks like this:
- app
FROMtools and(ADD . /app) - tools
FROMframework - framework
FROMOS - OS is the base container
Each container has its own Docker file.
Then, if we need to create another one app2, we can reuse our container framework . OK.
But if it app3comes along with the use of a similar container frameworks2 with slight differences from the frame , then we will get another image framework2 >.
This makes it very difficult to manage application versions with the image of the version and its databases.
Finally, I selected only one Docker file. APP is from the OS and it does everything, and Dockerfile does version control using the application.
Does anyone have any other ideas?
source
share