Compose
About versions and upgrading (Compose)
ASP.NET Core + SQL Server on Linux (Compose)
CLI environment variables (Compose)
Command-line completion (Compose)
Compose（組成）
Compose command-line reference（組合命令行參考）
Control startup order (Compose)
Django and PostgreSQL (Compose)
Docker stacks and distributed application bundles (Compose)
docker-compose build（docker-compose構(gòu)建）
docker-compose bundle
docker-compose config
docker-compose create
docker-compose down
docker-compose events
docker-compose exec
docker-compose help
docker-compose images
docker-compose kill
docker-compose logs
docker-compose pause
docker-compose port
docker-compose ps
docker-compose pull
docker-compose push
docker-compose restart
docker-compose rm
docker-compose run
docker-compose scale
docker-compose start
docker-compose stop
docker-compose top
docker-compose unpause
docker-compose up
Environment file (Compose)
Environment variables in Compose
Extend services in Compose
Frequently asked questions (Compose)
Getting started (Compose)
Install Compose
Link environment variables (deprecated) (Compose)
Networking in Compose
Overview of Docker Compose
Overview of docker-compose CLI
Quickstart: Compose and WordPress
Rails and PostgreSQL (Compose)
Sample apps with Compose
Using Compose in production
Using Compose with Swarm
Engine
.NET Core application (Engine)
About images, containers, and storage drivers (Engine)
Add nodes to the swarm (Engine)
Apply custom metadata (Engine)
Apply rolling updates (Engine)
apt-cacher-ng
Best practices for writing Dockerfiles (Engine)
Binaries (Engine)
Bind container ports to the host (Engine)
Breaking changes (Engine)
Build your own bridge (Engine)
Configure container DNS (Engine)
Configure container DNS in user-defined networks (Engine)
CouchDB (Engine)
Create a base image (Engine)
Create a swarm (Engine)
Customize the docker0 bridge (Engine)
Debian (Engine)
Default bridge network
Delete the service (Engine)
Deploy a service (Engine)
Deploy services to a swarm (Engine)
Deprecated Engine features
Docker container networking (Engine)
Docker overview (Engine)
Docker run reference (Engine)
Dockerfile reference (Engine)
Dockerize an application
Drain a node (Engine)
Engine
FAQ (Engine)
Fedora (Engine)
Get started (Engine)
Get started with macvlan network driver (Engine)
Get started with multi-host networking (Engine)
How nodes work (Engine)
How services work (Engine)
Image management (Engine)
Inspect the service (Engine)
Install Docker (Engine)
IPv6 with Docker (Engine)
Join nodes to a swarm (Engine)
Legacy container links (Engine)
Lock your swarm (Engine)
Manage nodes in a swarm (Engine)
Manage sensitive data with Docker secrets (Engine)
Manage swarm security with PKI (Engine)
Manage swarm service networks (Engine)
Migrate to Engine 1.10
Optional Linux post-installation steps (Engine)
Overview (Engine)
PostgreSQL (Engine)
Raft consensus in swarm mode (Engine)
Riak (Engine)
Run Docker Engine in swarm mode
Scale the service (Engine)
SDKs (Engine)
Select a storage driver (Engine)
Set up for the tutorial (Engine)
SSHd (Engine)
Storage driver overview (Engine)
Store service configuration data (Engine)
Swarm administration guide (Engine)
Swarm mode key concepts (Engine)
Swarm mode overlay network security model (Engine)
Swarm mode overview (Engine)
Understand container communication (Engine)
Use multi-stage builds (Engine)
Use swarm mode routing mesh (Engine)
Use the AUFS storage driver (Engine)
Use the Btrfs storage driver (Engine)
Use the Device mapper storage driver (Engine)
Use the OverlayFS storage driver (Engine)
Use the VFS storage driver (Engine)
Use the ZFS storage driver (Engine)
Engine: Admin Guide
Amazon CloudWatch logs logging driver (Engine)
Bind mounts (Engine)
Collect Docker metrics with Prometheus (Engine)
Configuring and running Docker (Engine)
Configuring logging drivers (Engine)
Control and configure Docker with systemd (Engine)
ETW logging driver (Engine)
Fluentd logging driver (Engine)
Format command and log output (Engine)
Google Cloud logging driver (Engine)
Graylog Extended Format (GELF) logging driver (Engine)
Journald logging driver (Engine)
JSON File logging driver (Engine)
Keep containers alive during daemon downtime (Engine)
Limit a container's resources (Engine)
Link via an ambassador container (Engine)
Log tags for logging driver (Engine)
Logentries logging driver (Engine)
PowerShell DSC usage (Engine)
Prune unused Docker objects (Engine)
Run multiple services in a container (Engine)
Runtime metrics (Engine)
Splunk logging driver (Engine)
Start containers automatically (Engine)
Storage overview (Engine)
Syslog logging driver (Engine)
tmpfs mounts
Troubleshoot volume problems (Engine)
Use a logging driver plugin (Engine)
Using Ansible (Engine)
Using Chef (Engine)
Using Puppet (Engine)
View a container's logs (Engine)
Volumes (Engine)
Engine: CLI
Daemon CLI reference (dockerd) (Engine)
docker
docker attach
docker build
docker checkpoint
docker checkpoint create
docker checkpoint ls
docker checkpoint rm
docker commit
docker config
docker config create
docker config inspect
docker config ls
docker config rm
docker container
docker container attach
docker container commit
docker container cp
docker container create
docker container diff
docker container exec
docker container export
docker container inspect
docker container kill
docker container logs
docker container ls
docker container pause
docker container port
docker container prune
docker container rename
docker container restart
docker container rm
docker container run
docker container start
docker container stats
docker container stop
docker container top
docker container unpause
docker container update
docker container wait
docker cp
docker create
docker deploy
docker diff
docker events
docker exec
docker export
docker history
docker image
docker image build
docker image history
docker image import
docker image inspect
docker image load
docker image ls
docker image prune
docker image pull
docker image push
docker image rm
docker image save
docker image tag
docker images
docker import
docker info
docker inspect
docker kill
docker load
docker login
docker logout
docker logs
docker network
docker network connect
docker network create
docker network disconnect
docker network inspect
docker network ls
docker network prune
docker network rm
docker node
docker node demote
docker node inspect
docker node ls
docker node promote
docker node ps
docker node rm
docker node update
docker pause
docker plugin
docker plugin create
docker plugin disable
docker plugin enable
docker plugin inspect
docker plugin install
docker plugin ls
docker plugin push
docker plugin rm
docker plugin set
docker plugin upgrade
docker port
docker ps
docker pull
docker push
docker rename
docker restart
docker rm
docker rmi
docker run
docker save
docker search
docker secret
docker secret create
docker secret inspect
docker secret ls
docker secret rm
docker service
docker service create
docker service inspect
docker service logs
docker service ls
docker service ps
docker service rm
docker service scale
docker service update
docker stack
docker stack deploy
docker stack ls
docker stack ps
docker stack rm
docker stack services
docker start
docker stats
docker stop
docker swarm
docker swarm ca
docker swarm init
docker swarm join
docker swarm join-token
docker swarm leave
docker swarm unlock
docker swarm unlock-key
docker swarm update
docker system
docker system df
docker system events
docker system info
docker system prune
docker tag
docker top
docker unpause
docker update
docker version
docker volume
docker volume create
docker volume inspect
docker volume ls
docker volume prune
docker volume rm
docker wait
Use the Docker command line (Engine)
Engine: Extend
Access authorization plugin (Engine)
Docker log driver plugins
Docker network driver plugins (Engine)
Extending Engine with plugins
Managed plugin system (Engine)
Plugin configuration (Engine)
Plugins API (Engine)
Volume plugins (Engine)
Engine: Security
AppArmor security profiles for Docker (Engine)
Automation with content trust (Engine)
Content trust in Docker (Engine)
Delegations for content trust (Engine)
Deploying Notary (Engine)
Docker security (Engine)
Docker security non-events (Engine)
Isolate containers with a user namespace (Engine)
Manage keys for content trust (Engine)
Play in a content trust sandbox (Engine)
Protect the Docker daemon socket (Engine)
Seccomp security profiles for Docker (Engine)
Secure Engine
Use trusted images
Using certificates for repository client verification (Engine)
Engine: Tutorials
Engine tutorials
Network containers (Engine)
Get Started
Part 1: Orientation
Part 2: Containers
Part 3: Services
Part 4: Swarms
Part 5: Stacks
Part 6: Deploy your app
Machine
Amazon Web Services (Machine)
Digital Ocean (Machine)
docker-machine active
docker-machine config
docker-machine create
docker-machine env
docker-machine help
docker-machine inspect
docker-machine ip
docker-machine kill
docker-machine ls
docker-machine provision
docker-machine regenerate-certs
docker-machine restart
docker-machine rm
docker-machine scp
docker-machine ssh
docker-machine start
docker-machine status
docker-machine stop
docker-machine upgrade
docker-machine url
Driver options and operating system defaults (Machine)
Drivers overview (Machine)
Exoscale (Machine)
Generic (Machine)
Get started with a local VM (Machine)
Google Compute Engine (Machine)
IBM Softlayer (Machine)
Install Machine
Machine
Machine CLI overview
Machine command-line completion
Machine concepts and help
Machine overview
Microsoft Azure (Machine)
Microsoft Hyper-V (Machine)
Migrate from Boot2Docker to Machine
OpenStack (Machine)
Oracle VirtualBox (Machine)
Provision AWS EC2 instances (Machine)
Provision Digital Ocean Droplets (Machine)
Provision hosts in the cloud (Machine)
Rackspace (Machine)
VMware Fusion (Machine)
VMware vCloud Air (Machine)
VMware vSphere (Machine)
Notary
Client configuration (Notary)
Common Server and signer configurations (Notary)
Getting started with Notary
Notary changelog
Notary configuration files
Running a Notary service
Server configuration (Notary)
Signer configuration (Notary)
Understand the service architecture (Notary)
Use the Notary client
?
本文檔使用 php中文網(wǎng)手冊 發(fā)布
文字
注意：只有在使用 Compose 文件格式的版本2或更高版本時，本文才適用。網(wǎng)絡(luò)功能不支持版本1（傳統(tǒng)）撰寫文件。
默認(rèn)情況下，組合設(shè)置一個網(wǎng)絡(luò)你的應(yīng)用程序。服務(wù)的每個容器都加入了默認(rèn)網(wǎng)絡(luò)，并且兩者都是?？蛇_(dá)網(wǎng)絡(luò)上的其他容器，以及可發(fā)現(xiàn)由它們在主機名上與容器名稱相同。
注：您的應(yīng)用程序的網(wǎng)絡(luò)是根據(jù)“項目名稱”命名的，該名稱基于它所在的目錄的名稱?？梢允褂?code>--project-name標(biāo)志或者
COMPOSE_PROJECT_NAME環(huán)境變量。
例如，假設(shè)應(yīng)用程序位于一個名為myapp，而你的docker-compose.yml看起來是這樣的：
version: "3"services: web: build: . ports: - "8000:8000" db: image: postgres ports: - "8001:5432"
當(dāng)運行docker-compose up的時候，發(fā)生如下情況：
myapp_default被創(chuàng)造了。
容器是使用
web的配置。它加入了網(wǎng)絡(luò)myapp_default以這個名字web。
容器是使用
db的配置。它加入了網(wǎng)絡(luò)myapp_default以這個名字db。
每個容器現(xiàn)在都可以查找主機名。web或db并獲取適當(dāng)容器的
IP 地址。例如，web的應(yīng)用程序代碼可以連接到
URL postgres://db:5432然后開始使用 Postgres 數(shù)據(jù)庫。
注意區(qū)分HOST_PORT和區(qū)分是重要的CONTAINER_PORT。在上面的例子中，db中，HOST_PORT是8001和容器端口是5432（postgres的默認(rèn)值）。網(wǎng)絡(luò)服務(wù)對服務(wù)通信使用CONTAINER_PORT。何時HOST_PORT被定義，該服務(wù)也可以在群外訪問。
在web容器，連接字符串到db看起來就像postgres://db:5432，從主機上看，連接字符串看起來像postgres://{DOCKER_IP}:8001...
更新容器
如果對服務(wù)進(jìn)行配置更改并運行docker-compose up要更新它，舊容器將被刪除，新容器將以不同的 IP 地址加入網(wǎng)絡(luò)，但名稱相同。正在運行的容器將能夠查找該名稱并連接到新地址，但舊地址將停止工作。
如果任何容器與舊容器有連接，則它們將被關(guān)閉。容器的責(zé)任是檢測此狀態(tài)，再次查找名稱并重新連接。
鏈接
鏈接允許您定義額外的別名，通過它可以從另一個服務(wù)訪問服務(wù)。他們不需要啟用服務(wù)進(jìn)行通信 - 默認(rèn)情況下，任何服務(wù)都可以以該服務(wù)的名稱到達(dá)任何其他服務(wù)。在以下示例中，db可以從web主機名db和以下位置訪問database：
version: "3"services: web: build: . links: - "db:database" db: image: postgres
見鏈接參考想了解更多信息。
多主機聯(lián)網(wǎng)
注意：本節(jié)中的指示信息涉及傳統(tǒng)的 Docker Swarm 操作，并且僅在針對傳統(tǒng) Swarm 集群時才起作用。有關(guān)將撰寫項目部署到較新的集成群模式的說明，請參閱 Docker Stacks 文檔。
何時將組合應(yīng)用程序部署到群集集群，您可以使用內(nèi)置的overlay驅(qū)動程序，以啟用容器之間的多主機通信，而不更改組合文件或應(yīng)用程序代碼。
請參閱多主機網(wǎng)絡(luò)入門以了解如何設(shè)置 Swarm 群集。群集將overlay默認(rèn)使用該驅(qū)動程序，但如果您愿意，您可以明確指定它 - 請參閱下文了解如何執(zhí)行此操作。
指定自定義網(wǎng)絡(luò)
您可以使用頂級networks密鑰指定您自己的網(wǎng)絡(luò)，而不只是使用默認(rèn)的應(yīng)用程序網(wǎng)絡(luò)。這使您可以創(chuàng)建更復(fù)雜的拓?fù)洳⒅付ㄗ远x網(wǎng)絡(luò)驅(qū)動程序和選項。您還可以使用它將服務(wù)連接到不受
Compose 管理的外部創(chuàng)建的網(wǎng)絡(luò)。
每項服務(wù)都可以使用服務(wù)級別 networks密鑰來指定要連接的網(wǎng)絡(luò)，服務(wù)級別密鑰是頂級 networks密鑰下引用條目的名稱列表。
以下是定義兩個自定義網(wǎng)絡(luò)的示例撰寫文件。proxy服務(wù)與服務(wù)是隔離的db，因為它們不共享共享的網(wǎng)絡(luò) - app只能與兩者通話。
version: "3"services: proxy: build: ./proxy networks: - frontend app: build: ./app networks: - frontend - backend db: image: postgres networks: - backend networks: frontend: # Use a custom driver driver: custom-driver-1 backend: # Use a custom driver which takes special options driver: custom-driver-2 driver_opts: foo: "1" bar: "2"
可以通過為每個連接的網(wǎng)絡(luò)設(shè)置 ipv4_address 和/或 ipv6_address 來為網(wǎng)絡(luò)配置靜態(tài) IP 地址。
有關(guān)可用網(wǎng)絡(luò)配置選項的詳細(xì)信息，請參閱下列參考資料：
頂層
networks鍵
服務(wù)級
networks鍵
配置默認(rèn)網(wǎng)絡(luò)
除了指定您自己的網(wǎng)絡(luò)外，您還可以通過在networks名稱下定義條目來更改應(yīng)用程序范圍的默認(rèn)網(wǎng)絡(luò)的設(shè)置default：
version: "3"services: web: build: . ports: - "8000:8000" db: image: postgres networks: default: # Use a custom driver driver: custom-driver-1
使用預(yù)先存在的網(wǎng)絡(luò)
如果希望容器加入現(xiàn)有網(wǎng)絡(luò)，請使用external期權(quán)*
networks: default: external: name: my-pre-existing-network
而不是試圖創(chuàng)建一個名為[projectname]_default，將尋找一個名為my-pre-existing-network并將應(yīng)用程序的容器連接到它。