Does hub.docker.com use “–no-cache” for automated builds?
I am analysing some slightly strange behaviour in our automated build processes, which lead me to ask:
Does hub.docker.com use the
--no-cache option when performing automated builds?
2 Solutions collect form web for “Does hub.docker.com use “–no-cache” for automated builds?”
Yes. The build process is currently:
git clone --recursive --depth 1 -b branch $URL
docker build -t tagname --nocache
- Tar and upload the build context to S3 bucket
- Push image (with all layers) to Registry
- Worker or Builder cleans up build residue (mounted volumes, etc)
Unfortunately, this was not the case for me. I had to end up rebuilding the image with the –no-cache flag. Then push the image up to docker hub.
Admittedly the dockerfile used was not with best practice as it involved a “git pull”. Oh well!