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构建）
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中文網手册 發布
文字
您正在查看传统独立群组的文档。这些主题描述了独立的 Docker Swarm。在 Docker 1.12 及更高版本中，Swarm 模式与 Docker Engine 集成。大多数用户应该使用集成的 Swarm 模式 - 一个好的开始就是 Swarm 模式入门， Swarm 模式 CLI 命令以及 Docker 演练入门。独立 Docker Swarm 未集成到 Docker Engine API 和 CLI 命令中。
Docker Compose 和 Docker Swarm 旨在实现完全集成，这意味着您可以将一个Compose应用程序指向一个 Swarm 集群，并且只需像使用单个 Docker 主机一样工作即可。
实际的集成范围取决于您使用的 Compose 文件格式的版本：
如果您使用的是版本1
links，则您的应用程序可以正常工作，但Swarm会将所有容器安排在一台主机上，因为容器之间的链接不适用于使用旧网络系统的主机。
如果您使用的是第2版，则您的应用程序应该无任何更改：
- subject to the [limitations](index#limitations) described below,- as long as the Swarm cluster is configured to use the [overlay driver](../../engine/userguide/networking/index#an-overlay-network-with-docker-engine-swarm-mode), or a custom driver which supports multi-host networking.
阅读多主机网络入门以了解如何使用 Docker Machine 和覆盖驱动程序设置 Swarm 群集。运行后，将应用程序部署到该应用程序应该如此简单：
$ eval "$(docker-machine env --swarm <name of swarm master machine>)"$ docker-compose up
局限性
构建图像
Swarm 可以像 Docker 实例一样通过 Dockerfile 构建镜像，但生成的镜像只能存在于单个节点上，不会分配给其他节点。
如果您想使用 Compose 将服务扩展到多个节点，则必须自己构建它，将其推送到注册表（例如 Docker Hub）并从docker-compose.yml以下位置引用它：
$ docker build -t myusername/web .$ docker push myusername/web $ cat docker-compose.yml web: image: myusername/web $ docker-compose up -d $ docker-compose scale web=3
多重依赖
如果一个服务具有强制联合调度类型的多个依赖关系（参见下面的自动调度），那么 Swarm 可能会调度依赖关系到不同的节点上，从而无法安排依赖服务。例如，这里foo需要被共同调度与bar和baz：
version: "2"services: foo: image: foo volumes_from: ["bar"] network_mode: "service:baz" bar: image: bar baz: image: baz
问题是，群可能会先安排bar和baz不同的节点上（因为他们是不依赖于彼此），使它不可能挑选一个合适的节点foo。
要解决此问题，请使用手动调度来确保所有三个服务都在同一个节点上结束：
version: "2"services: foo: image: foo volumes_from: ["bar"] network_mode: "service:baz" environment: - "constraint:node==node-1" bar: image: bar environment: - "constraint:node==node-1" baz: image: baz environment: - "constraint:node==node-1"
主机端口和重新创建容器
如果服务从主机映射端口，例如80:8000，那么docker-compose up在第一次之后运行它时可能会出现类似下面的错误：
docker: Error response from daemon: unable to find a node that satisfies container==6ab2dfe36615ae786ef3fc35d641a260e3ea9663d6e69c5b70ce0ca6cb373c02.
这种错误的常见原因是容器在没有显式映射的情况下具有一个卷（在其图像或撰写文件中定义），因此为了保留其数据，Compose 已指示 Swarm 安排新容器与旧容器相同的节点。这导致了端口冲突。
解决这个问题有两个可行的解决办法：
指定一个已命名的卷，并使用一个卷驱动程序，该卷驱动程序能够将该卷挂载到容器中，而不管其预定在哪个节点上。如果服务仅使用命名卷，则Compose不会为Swarm提供任何特定的计划指示。版本：“2”服务：web：build：。端口： - “80：8000”卷： - web-logs：/ var / log / web卷：web-logs：driver：custom-volume-driver
在创建新容器之前删除旧容器。您将失去该卷中的任何数据。
$ docker-compose stop web
$ docker-compose rm -f web
$ docker-compose up web
调度容器
自动调度
某些配置选项将导致容器在同一个 Swarm 节点上自动进行调度，以确保它们正常工作。这些是：
network_mode: "service:..."和network_mode: "container:..."（以及net: "container:..."第一版文件格式）。
volumes_from
links
手动调度
Swarm 提供了丰富的时间安排和亲和力提示，使您能够控制容器的位置。它们通过容器环境变量指定，因此您可以使用Compose 的environment选项来设置它们。
# Schedule containers on a specific node environment: - "constraint:node==node-1"# Schedule containers on a node that has the 'storage' label set to 'ssd'environment: - "constraint:storage==ssd"# Schedule containers where the 'redis' image is already pulled environment: - "affinity:image==redis"
有关完整的可用过滤器和表达式，请参阅 Swarm 文档。