使用 Docker Compose 构建多容器应用
使用 Docker Compose 通过单个声明式文件定义并运行多服务应用（应用、数据库和缓存）。
使用 Docker Compose 构建多容器应用 是 CoddyKit 上的免费 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课时。 这是第 4 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 AI Powered SaaS: Stripe + Auth + Billing + Deploy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Why Docker Compose?
Real apps rarely run in one container. You often need a web app, a database, and a cache. Docker Compose lets you define all of them in one YAML file and start them with a single command.
The compose.yaml File
Compose reads a file named compose.yaml (or docker-compose.yml). Each entry under services describes one container.
services:
web:
build: .
ports:
- "3000:3000"
db:
image: postgres:16Defining a Service
A service can be built from a local Dockerfile or pulled as an existing image. You also set ports, environment variables, and dependencies here.
Environment Variables
Pass configuration with environment or load from an .env file. Never hardcode secrets directly in the YAML committed to git.
services:
db:
image: postgres:16
environment:
POSTGRES_PASSWORD: ${DB_PASSWORD}Service Networking
Compose puts all services on a shared network. A service reaches another by its service name as the hostname. The web app connects to the database at db:5432.
Persisting Data with Volumes
Containers are ephemeral. Use a named volume so database data survives restarts and rebuilds.
services:
db:
image: postgres:16
volumes:
- dbdata:/var/lib/postgresql/data
volumes:
dbdata:Startup Order with depends_on
depends_on controls start order, but it does not wait for a service to be ready. Combine it with a healthcheck so the web app waits until the database accepts connections.
Bringing It Up and Down
Start everything in the background with up -d and stop with down. Add --build to rebuild images after code changes.
docker compose up -d --build
docker compose downViewing Logs
Aggregate logs from all services or follow one. This is essential for debugging how containers interact.
docker compose logs -f webScaling a Service
Run multiple copies of a stateless service to handle more load. Put a load balancer or reverse proxy in front to distribute traffic.
docker compose up -d --scale web=3Compose for Dev vs Production
Use a base compose.yaml plus an override file for each environment. Development might mount source code for hot reload; production uses prebuilt images and stricter restart policies.
Quick Check
Check your Docker Compose knowledge.
Recap
You learned to orchestrate multi-container apps with Docker Compose:
- Define services in
compose.yaml - Connect them via service-name networking
- Persist data with volumes and control order with depends_on/healthcheck
- Use
up,down, logs, and scaling
Compose makes local and production multi-service setups reproducible.
常见问题解答
「使用 Docker Compose 构建多容器应用」课时是免费的吗？
是的 — 「使用 Docker Compose 构建多容器应用」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课程的其余内容，请升级到 CoddyKit PRO。 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课程共包含 4 节课。
「使用 Docker Compose 构建多容器应用」这节课中我会学到什么？
使用 Docker Compose 通过单个声明式文件定义并运行多服务应用（应用、数据库和缓存）。 你通过在浏览器中直接运行的动手代码来练习 AI Powered SaaS: Stripe + Auth + Billing + Deploy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 AI Powered SaaS: Stripe + Auth + Billing + Deploy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 4 节课，共 4 节。
「使用 Docker Compose 构建多容器应用」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课中编写并运行代码吗？
能。每节 AI Powered SaaS: Stripe + Auth + Billing + Deploy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。