Why You Should be Using Multi-stage Docker Builds in 2019
0 likes1,012 views
This document discusses the benefits of using multi-stage Docker builds. It notes that traditional Docker builds result in large images containing build tools and files not needed for runtime. Multi-stage builds address this by allowing builders to create multiple stages, each producing a new image, to arrive at a minimal final image containing only what is needed for production. This improves build speed and produces more secure images by removing unnecessary components. Multi-stage builds can be used across many programming languages and are supported in continuous integration/deployment on platforms like Codefresh.
Why You Should be Using Multi-stage Docker Builds in 2019
- 1. Why you should be using Multi-Stage Docker Builds in 2019 GUY SALTON
- 3. Agenda ● The problem with Docker build ● Solution: Docker multi-stage build ● Docker multi-stage build in CI/CD ● Summary ● Dockerfile and Docker build https://github.com/codefresh-contrib/golang-sample-app/ https://codefresh.io/docs/docs/learn-by-example/golang/golang-hello-world/
- 4. Docker multi-stage build ● “oh man! thank you! I've been fighting with build times on an image stack for weeks” ● “Wow, this is great for deploying tonnes of microservices!” ● “I've been meaning to use multistage builds, thanks for the walkthrough!” https://www.reddit.com/r/golang/comments/crkibq/docker_golang_reducing_container_size_using/ Multi-stage build is available starting from Docker 17.05 (released in 2017!) - so why now?
- 5. Dockerfile and Docker build ● Dockerfile - imperative DSL that defines build commands ● Each Docker build command generates ONE image layer ● Complete Docker build execution generates ONE Docker image
- 6. Dockerfile and Docker build
- 7. Demo 1: Docker build on GO app https://github.com/codefresh-contrib/helm-sample-app
- 8. The Problem with Docker build Image we want Image we build runtime configuration application Compilers, debuggers, ... Linters, tests, profilers, ... code, build and test logs, ... runtime configuration application X (4..10)
- 9. The Problem with Docker build ● 2 Dockerfiles ○ 1st for build tools ○ 2nd for runtime ● Drawbacks ○ 2+ Dockerfiles ○ Orchestration needed: Bash, make, YAML, ...
- 10. Solution: Docker multi-stage build ● Benefits ○ One Dockerfile ○ One syntax to learn ○ Same build ■ Local and CI ○ Create multiple stages
- 11. guy.salton@codefresh.io FROM: alpine:3.5 curl FROM: ubuntu /hello FROM: debian /world FROM: base /hello /world
- 12. Demo 2: Docker multi-stage build
- 13. Docker multi-stage build You can enjoy multi-stage build with every programming language (not only GO): ● GO example - https://codefresh.io/docs/docs/learn-by-example/golang/golang-hello-world/#create-a-multi-stage-docker-image-for-go ● JAVA example - https://codefresh.io/docs/docs/learn-by-example/java/spring-boot-2/#spring-boot-2-and-docker-multi-stage-builds ● Node example - https://codefresh.io/docs/docs/learn-by-example/nodejs/react/#react-and-docker-multi-stage-builds ● PHP example - https://codefresh.io/docs/docs/learn-by-example/php/#the-example-php-project https://codefresh.io/containers/docker-anti-patterns/Docker anti-patterns
- 14. Codefresh The 1st container-native CI/CD Platform for Microservices Container-native Intuitive & Robust Enterprise Ready Flexible Delivery
- 15. Demo 3: Docker multi-stage build in CI/CD
- 16. Summary ● Using 1 Docker image for both build and production results in slow deployment and lots of CVE violations ● Multi-stage build to produce lean, secure and production ready Docker image ● On Codefresh, speedier builds thanks to caching across all images and layers
- 17. Signup for a FREE account with UNLIMITED builds & schedule a 1:1 with our experts at https://codefresh.io Build Fast, Deploy Faster Thank You! guy.salton@codefresh.io