Following step is not being cached by the docker build process which takes a lot of time and storage both while building the container and while pushing it to the private registry:
Steps to reproduce:
1) Build the image with docker build -t asvs .
2) Make any change, for example add new allowed host to asvs/settings.py
3) Build image again with docker build -t asvs .
4) Watch mentioned step being executed again
~I guess it's because of --no-cache flag so I was wondering what is the reason for using it~? Would there be a way to make this build step cacheable?
EDIT:
--no-cache flag doesn't seem to be a cause here (I tried without it)
Following step is not being cached by the docker build process which takes a lot of time and storage both while building the container and while pushing it to the private registry:
Steps to reproduce: 1) Build the image with
docker build -t asvs .2) Make any change, for example add new allowed host toasvs/settings.py3) Build image again withdocker build -t asvs .4) Watch mentioned step being executed again~I guess it's because of
--no-cacheflag so I was wondering what is the reason for using it~? Would there be a way to make this build step cacheable?EDIT:
--no-cacheflag doesn't seem to be a cause here (I tried without it)