During the build process, make builds a docker container image, uniquely tag it, and launch my python application and server instances to run tests, and exits. Although it pollutes my docker registry.
# docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
docker-priac-base.af.abc.local/fmd/app-sanity-1.0.0.0 21.userid 7167b8f30add 9 minutes ago 156MB
docker-priac-base.af.abc.local/fmd/app-sanity-1.0.0.0 22.userid 6167d8f30add 19 minutes ago 156MB
My application needs lots of dependencies and takes time to download them and make a container ready to run. So if after running the test if I remove the image, all dependencies are downloaded again. If I keep the image then the docker registry is polluted. As a new build will create a new tag, how docker avoids download dependencies.
Although I can create a pre-downlaod dependencies as a base docker image to speed up the process I am trying to understand what I a missing here. All these images are separately tagged, why next image is any faster?
question from:https://stackoverflow.com/questions/65943925/running-tests-in-container-pollutes-docker-registry
