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?

  • Build Java Gradle project within a Docker container?
  • Should I add the reverse proxy in the same container as the application on docker?
  • FileNotFoundException in tomcat7 running inside a ubuntu docker container
  • nginx no such file or directory
  • How to set the Docker IP the same as your computer (local) IP address
  • creating a docker container from a rootfs
  • Possible to use Docker machine with continuous integration tools?
  • Can I dockerize Activex exe which has GUI?
  • Cannot connect to mongodb instance from docker: Connection refused
  • Deploying latest docker containers with ansible
  • connecting to AWS server where docker is deployed through template
  • How to edit ENTRYPOINT file of a docker image.
  • 2 Solutions collect form web for “Does hub.docker.com use “–no-cache” for automated builds?”

    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)

    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!

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.