CODEWITHSUNDEEP
dockerdockerhub
tbsalling
tbsalling

Reputation: 4555

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?

Upvotes: 11

Views: 2229

Answers (2)

djsd123
djsd123

Reputation: 413

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!

Upvotes: 1

Andy
Andy

Reputation: 38317

Yes. The build process is currently:

  1. git clone --recursive --depth 1 -b branch $URL
  2. Extract Readme and Dockerfile
  3. docker build -t tagname --nocache
  4. Tar and upload the build context to S3 bucket
  5. Push image (with all layers) to Registry
  6. Worker or Builder cleans up build residue (mounted volumes, etc)

Upvotes: 22

Related Questions