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 run: what a container really is on the server

What happens when you put your app in a Docker container

Linux namespaces: why a container thinks it is alone

A Docker container runs on a busy server, next to hundreds of other programs. From inside, the container sees none of them. It even believes that the name of the server is its own name.

  1. 1 The container runs, but Miva still can't reach the request page. From the inside, the container sees nobody, so it thinks it is alone. Yet plenty of other processes run right next to it, on the same server.inside the serverremote logintimerDockerthe containerAnyone here? No?Just me, then!

    The container runs, but Miva still can't reach the request page. From the inside, the container sees nobody, so it thinks it is alone. Yet plenty of other processes run right next to it, on the same server.

  2. 2 So the same server holds two pictures: the one the container sees, empty, and the real one, busy all around it. Someone hides the others from the container. But who?what it seeswhat is there

    So the same server holds two pictures: the one the container sees, empty, and the real one, busy all around it. Someone hides the others from the container. But who?

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

Next episode Port publishing: how a request from outside reaches a container

Share this comic

More comics