Back to the study

Learning term

Service discovery — Compose, Swarm, and Portainer

Service discovery connects services across the cluster and resolves their logical names. This card shows its role in “Compose, Swarm, and Portainer” and a safe diagnostic path.

Compose, Swarm, and PortainerLevel 0–3

Orientation

Service discovery connects services across the cluster and resolves their logical names. At this level, separate purpose, input, and visible result. Place Service discovery within Compose, Swarm, and Portainer before changing settings or files.

Exercise

Try it safely

Test DNS and the target port from a task when service-to-service traffic fails. Open an isolated test environment and run “docker service ls && docker service ps example-service”. Write down the expected output first, do not alter production data, and record one safe next diagnostic step.

docker service ls && docker service ps example-service

Quick check

Can you explain the purpose, observable state, and most common failure source of Service discovery — Compose, Swarm, and Portainer in one sentence each? Which evidence would you preserve before changing anything, and which repeated test would prove that the correction actually worked?