3 minutes read
I was honored to talk about a Docker image team journey at Dev Ops Pro 2019 Conference in Vilnius, Lithuania. The talk outlines options how to reduce docker images with respect to:
- docker image size
- attack surface
These are the slides:
Actually I did a very similar talk already at Berlin CI/CD Meetup 2018. To prepare the talk in Vilnius in 2019, I updated the hellogodocker sample golang project to golang v1.12 – the 2018 version is based on golang v1.11.
Every commit in the hellogodocker sample golang project triggers a build on circleCI hellogodocker project project. Every build creates new docker images in hellogo project on dockerhub. I refer to the circleCI build #105 for my slide deck.
Comparing the 2018 and 2019 numbers reveals an interesting detail:
In 2018, the docker image build time was reduced from 3 seconds to ~0,5 seconds using docker build –cache-from flag. This is not the case anymore in 2019. This difference is reflected in the slides:
as well as in the CircleCI builds
All other relevant numbers remain the same in both, the 2018 and 2019 version.
Both, the 2019 and 2018 version of the slides are also available on speakerdeck:
- 2018 — docker image journey – how to shrink a docker image
- 2019 — docker image journey – how to shrink a docker image