Docker Compose and YAML, Explained Simply for Linux users
A long `docker run` command works once, then the exact setup lives only in your shell history. Docker Compose lets you write the whole thing down: one file, one command, the whole system.
This episode builds the mental model behind Compose, one idea at a time:
• Image vs container: the blueprint and the running thing
• What compose.yaml actually is
• Why YAML indentation IS the structure, not decoration
• What 8080:80 really means (host port vs container port)
• Why volumes outlive the containers that use them
• depends_on and environment between services
• docker compose up / ps / logs / exec / down
Chapters
0:00 One command, a lot to remember
0:22 Image vs container
0:52 Write it down: compose.yaml
1:18 Indentation is the structure
1:46 Ports: a tunnel to the host
2:22 Volumes outlive containers
3:02 Services that need each other
3:36 compose up wakes the file
4:04 Up, inspected, and down
4:31 The mental model
The whole idea: a compose file is one readable description of your app and one command brings it to life.
—
Code on Principles makes beginner-friendly programming tutorials where the code, narration, and visuals move together. Code-rendered: scripted scenes, timed narration, animated edits. Small ideas, clearly seen.