Creating Effective Docker Images

Sick of getting paged at 2am and wondering "where did all my disk space go?" This has actually happened to me, and you can learn from my mistakes! New Docker users often start with a stock image in order to get up and running quickly, but that isn't always the right answer. Creating efficient images is often overlooked, but important. Beyond saving resources, using minimal images also delivers important security benefits: include only what you need and not a whole runtime that might have security vulnerabilities. In this session, I'll talk about how to create effective images and lessons I've learned from running containers in production at a number of startups. I'll also cover topics like "how do layers work?" and some things you should think about when creating your images, such as; choosing or creating the right base image; the importance of caching; using RUN statements conservatively; cleaning up as you go. I'll also address best practices; both at a high level with multi-stage builds; and some language-specific best practices, for example, tips and tricks for creating containers for Node.js vs Go. To illustrate these points, we'll cover: * How layers work? * Choosing a base image vs. creating your own * The basics of building minimal images and the importance of choosing a base image vs. creating your own * The basics of building minimal images and the importance of caching * High level best practices for Linux containers (in general, and some language specific examples) * High level best practices for Windows container images * New and improved: multi-stage builds * Good vs. not so good Dockerfile examples * Docker Image Scanning, and other friends * What's up next? Looking to the future for more optimization.

[@andrewedwards3970]

This is simply a great presentation: clear, concise, professional. People complaining about use of the word "so"? "So what" I say, it was great, free, and perfectly scoped.

[@lyingcat9022]

Cache rules everything around me, docker docker builds y’all!

[@debapriyag]

But the disk sizes are not calculated on the number of containers multiplied by the base image. The base image still will be using just one times its own size irrespective of the number of containers being spun from it. Only the writable layer keeps adding to the disk size for each container.

[@lyingcat9022]

Haha great talk :) New to using Docker and this pointed out some good stuff I might not have thought about right away. Thanks

[@sergeileshchinsky]

Great presenter. Keep up!

[@user-fs8on7xi9i]

Good Speech.

[@qiny9772]

great!

[@mr.august1]

I like her "so" :)

[@naoualinizar3573]

like u Abby

[@Rogueixpresents]

Why these images are so big? I legit do not understand it

[@lyingcat9022]

Cache me outside, how bout dat?

[@RELO4D3D1]

Good stuff! Advice to speaker is to try to stop using "so" as a stop / pause word, otherwise great presentation.

[@ZFlyingVLover]

Better than using 'Um'

[@donwald3436]

um, so