You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Docker container vs virtual machine: what is really different underneath

What happens when you put your app in a Docker container

Docker build cache: what a new version of your app rebuilds, pushes and pulls

You fix one line of your app. Docker must build a new image, because an image never changes after it is built. With the right Dockerfile, the new build skips almost every step. With the steps in the wrong order, it does nearly all of them again.

  1. 1 Back on your laptop, you find the bug: one line kept some memory for each request. You delete it, and version 1.1 is ready, while the server still runs 1.0.you1.1RonoIs it on theserver yet?

    Back on your laptop, you find the bug: one line kept some memory for each request. You delete it, and version 1.1 is ready, while the server still runs 1.0.

  2. 2 Version 1.0 carried every layer of its image to the registry, then to the server. Will 1.1 have to carry them all again?your laptopcopy your appadd dependenciesbase imageregistryserver

    Version 1.0 carried every layer of its image to the registry, then to the server. Will 1.1 have to carry them all again?

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

You finished the comic Back to the comic

Share this comic

More comics