Skip to content
Français
Account: not signed in, sync available My learning
Select theme
Français

Skill · Containers · Build and run containers

Describe and harden a multi-service application with Docker Compose: variables, networks, data, secrets, health, resources and variants

Describe a multi-service application in a compose.yaml and check what Compose will create with docker compose config, drive its lifecycle (up, stop, down, down -v) under a project name, control interpolation and the precedence of environment files, spread services over networks, some of them internal, keep a database's data across every recreation and grant a file secret to a single service while knowing its limits. Then make it reliable: declare a healthcheck and make a service or a migration wait with depends_on conditions, knowing that an unhealthy service is not restarted and that the client must retry; limit memory, CPU and processes and check the limit in the cgroup, recognise an OOMKilled container, choose a restart policy, know what it restarts and tune the grace period; assemble a base and named variants with -f, predict how they merge and clear an inherited key with !reset, reserve a service for a profile, find a project's files with docker compose ls and use docker compose watch.

Start lesson 1The Containers domain

Lessons

How to learn it

8 lessons, about ~11 h 35, in program order. Each lesson ends with its quiz.

The program

8 lessons · ~11 h 35

Beyond the lessons

Assess, practise, pass the proof

Reading a lesson confirms nothing. A skill is confirmed by a passed quiz, practised in a guided lab, and put to the test by a challenge or a mission; an imported lab result is not verified by the site.

Around it

Who requires it, who teaches it

Is this project useful to you?

The guides, courses, quizzes and labs stay free. If you use them regularly, you can contribute to their upkeep and development.

Become a supporting member (new tab) One-time support (new tab) Learn more

Follow the project on LinkedIn