Linux Labs
Where to start First steps track · 15 stages
Linux Labs
EN

Containers: Docker and compose

Image and container, ports, environment and restart, your own Dockerfile, volumes, container networking and a compose stack, memory limits and the user inside a container.

11 stages5 labs~6 hours medium medium

Progress Stages: 0 of 11

The track has not been started. The first stage is «Image, container and process», ~30 min.

Start stage 1

Module 1

A container from the inside

How an image differs from a container, why a container exited at once, how to publish a port, pass the environment and set a restart policy.

3 stages · ~2 hours

  1. Stage 1 of 11

    1 · Image, container and processImage, container and process

    6 steps · ~30 min 6 steps · ~30 min
    1. The web server started and vanished exercises 0 of 1 on a machine 5 min
    2. 2 Image and container on a machine 6 min
    3. 3 A container lives while its process runs on a machine 8 min
    4. 4 Inside the container on a machine 5 min
    5. 5 Experiment: a container from alpine on a machine 4 min
    6. 6 Summary summary 2 min
    Start stage 1
  2. Stage 2 of 11

    2 · Ports, variables and restartPorts, variables and restart

    8 steps · 2 labs · ~1 hour 8 steps · 2 labs · ~1 hour
    1. The container runs, the site is silent exercises 0 of 1 on a machine 5 min
    2. 2 Container port and server port on a machine 7 min
    3. 3 Environment variables on a machine 6 min
    4. 4 Restart policy theory 6 min
    5. 5 Experiment: a queue that comes back by itself on a machine 4 min
    6. 6 Container won't start medium lab 20 min
    7. 7 A service from a container medium lab 20 min
    8. 8 Summary summary 2 min
    Start stage 2
  3. 3 · Module test 10 questions · pass mark 70%

Module 2

Images and data

How to build an image from a Dockerfile, where the layer cache works, where container data lives and how to keep it in a volume or a host directory.

3 stages · ~2 hours

  1. Stage 4 of 11

    4 · Dockerfile: your own imageDockerfile: your own image

    7 steps · 1 lab · ~50 min 7 steps · 1 lab · ~50 min
    1. The edit did not arrive exercises 0 of 1 on a machine 5 min
    2. 2 An image is built from a Dockerfile on a machine 7 min
    3. 3 Layers and tags theory 5 min
    4. 4 The build cache on a machine 7 min
    5. 5 Your own storefront on nginx on a machine 4 min
    6. 6 A new image version medium lab 20 min
    7. 7 Summary summary 2 min
    Start stage 4
  2. Stage 5 of 11

    5 · Volumes: data outlives the containerVolumes: data outlives the container

    7 steps · 1 lab · ~50 min 7 steps · 1 lab · ~50 min
    1. The notes are gone exercises 0 of 1 on a machine 5 min
    2. 2 The container layer theory 5 min
    3. 3 A named volume on a machine 7 min
    4. 4 A host directory on a machine 6 min
    5. 5 A report through nginx on a machine 5 min
    6. 6 Data after re-creation medium lab 20 min
    7. 7 Summary summary 2 min
    Start stage 5
  3. 6 · Module test 10 questions · pass mark 70%

Module 3

Several containers

How containers find each other by name, how to describe a stack in one file and diagnose its failure with compose ps and logs.

3 stages · ~1 hour

  1. Stage 7 of 11

    7 · Container networking: names and portsContainer networking: names and ports

    6 steps · ~30 min 6 steps · ~30 min
    1. The application cannot find its database exercises 0 of 1 on a machine 6 min
    2. 2 The default network on a machine 7 min
    3. 3 A network of your own: names work on a machine 6 min
    4. 4 The neighbour's port theory 5 min
    5. 5 Experiment: the reports service on a machine 4 min
    6. 6 Summary summary 2 min
    Start stage 7
  2. Stage 8 of 11

    8 · docker compose: a stack in one filedocker compose: a stack in one file

    7 steps · ~30 min 7 steps · ~30 min
    1. The site answers 502 exercises 0 of 1 on a machine 5 min
    2. 2 The stack file on a machine 6 min
    3. 3 Editing and re-creating on a machine 5 min
    4. 4 Volumes and down theory 4 min
    5. 5 Health checks theory 4 min
    6. 6 Experiment: the notes stack on a machine 4 min
    7. 7 Summary summary 2 min
    Start stage 8
  3. 9 · Module test 10 questions · pass mark 70%

Module 4

Container resources and security

How to limit the memory and CPU of a container, what exit code 137 and OOMKilled mean and how to run the process as non-root.

2 stages · ~1 hour

  1. Stage 10 of 11

    10 · Limits, OOMKilled and the user in a containerLimits, OOMKilled and the user in a container

    9 steps · 1 lab · ~55 min 9 steps · 1 lab · ~55 min
    1. The report broke off exercises 0 of 1 on a machine 4 min
    2. 2 The memory limit and the OOM killer theory 6 min
    3. 3 How much a container takes on a machine 4 min
    4. 4 The CPU quota theory 4 min
    5. 5 Who runs in the container on a machine 4 min
    6. 6 The --user option theory 3 min
    7. 7 The report to the end on a machine 3 min
    8. 8 A container restarts under load medium lab 25 min
    9. 9 Summary summary 2 min
    Start stage 10
  2. 11 · Module test 9 questions · pass mark 70%

  1. Final lab

    A compose stack after the move ~40 min
  2. Final test 18 questions · pass mark 80%

What to know beforehand

Articles of the current stage

Already know this?

Take the final test right away: with 80% or more the whole track counts as passed.

Skip the track with a test
Loading…