We're using the Cloudbees Docker Build and Publish plugin to build Docker images in our Jenkins instance. The builds are working fine and we're pushing to Docker Hub successfully, but the images are sticking around on the Jenkins slave and causing space issues.
Is there an option to remove the images after a successful build and push? Thanks.
Like you said, you need to have --rm as an Additional Build Arguments in advanced section of Cloudbees Docker Build and Publish plugin to get rid of those intermediate container but images that you build and push to repo will still remain on your host. Simple fix would be to add a build step and execute a shell command like this to delete those images:
docker rmi ACCOUNT/IMAGE:${BUIL_NUMBER}
Assuming you're tagging your images with Jenkins BUILD_NUMBER, you can replace it with whatever variable that you use.
Additional Build Argumentstextfield where you can add build flags like--rm. - ivan.sim0cee7a3ced47is a parent image. Have you tried other ways to reduce your image size such as using a smaller base image, chain multipleRUNwith&&, use multiple variables forENV,EXPOSEetc. Every instruction in your Dockerfile adds a layer to your container image. - ivan.sim