0% completed

All LessonsFree Lessons (5)

Before Getting Started

Why Docker?

A DevOps Enabler Tool Solves Dependency Conflicts Allows Easy Scaling Up Allows Seamless Upgrades International Commerce Already Uses Containers Quiz

Get Docker up and Running

Various Products for Various Needs Community on a Developer or CI Machine

Basic Concepts

Basic Concepts Quiz

Use Docker Images

Do-It-Yourself: Run a Container Container Management Commands Do-It-Yourself: Post-Mortem Inspection More About Docker Run Running a Server Container Exercise: Run a Server Container Exercise Solution Using Volumes Where Do Images Come From?Quiz

Create Docker Images

Creating a Simple Image Creating an Image Including Files Images Are Created Locally Exercise: Build an Image and Run It Exercise Solution Tags Matter Parameters as Environment Variables Exercise: Enable an Image to Be Parameterized Exercise Solution Storage Networking Learning More Quiz

Publish Docker Images

Rationale for Publishing Registries Publishing an Image Docker Hub Run an Image on Another Machine Exercise: Publish an Image and Run a Container on Another Machine Exercise Solution Private Registries Size Matters Quiz

Forget SDK Installs

One Tool to Rule Them All

Building Rationally: Easy CI

Multi-Stage Dockerfiles

Docker with Common Development Profiles

Introduction Java Node.js PHP .NET Core Python

More About Running Containers

Restart Mode Monitoring Reclaim Your Disk Orchestration Basics

Docker for Developers/

...

/

Multi-Stage Dockerfiles

Multi-Stage Dockerfiles

In this lesson, we will learn how to handle large images using multi-stage Dockerfiles.

We'll cover the following...

The problem with the image we created above is that it’s massive; it’s 1730 MB! This is because it contains the build tools we don’t need, tools like dotnet restore and dotnet publish. Also, it contains the source code and intermediate build artifacts.

We could use the RUN command to try and clean the image; delete intermediate build artifacts, uninstall build tools, and delete source code, but that would be tedious. Remember that containers are like cheap, disposable ...