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
©
Dieses Dokument verwendet PHP-Handbuch für chinesische Websites Freigeben
Figuren
本节中的信息说明在 Docker 默认网桥中配置容器 DNS。这是一个在安装 Docker 时自动创建名为bridge的bridge网络。
注意：通过 Docker 网络功能，您可以创建除默认网桥以外的用户定义网络。有关用户定义网络中 DNS 配置的更多信息，请参阅 Docker Embedded DNS 部分。
Docker 如何为每个容器提供主机名和 DNS 配置，而不必使用内部写入的主机名来构建自定义映像？它的诀窍是/etc用虚拟文件覆盖容器内的三个关键文件，以便在其中写入新的信息。您可以通过mount在容器中运行来看到这一点：
root@f38c87f2a42d:/# mount... /dev/disk/by-uuid/1fec...ebdf on /etc/hostname type ext4 ... /dev/disk/by-uuid/1fec...ebdf on /etc/hosts type ext4 ... /dev/disk/by-uuid/1fec...ebdf on /etc/resolv.conf type ext4 ......
这种安排允许 Docker 做一些聪明的事情，例如resolv.conf当主机在稍后通过
DHCP 接收新的配置时，在所有容器中保持最新状态。Docker 如何在容器中维护这些文件的确切细节可以从一个 Docker 版本更改为下一个，因此您应该保留文件本身，并改为使用以下 Docker 选项。
四个不同的选项影响容器域名服务。
-h HOSTNAME或--hostname = HOSTNAME | 设置容器知道自己的主机名。这写入/ etc / hostname，写入/ etc / hosts 作为容器的面向主机的IP地址的名称，并且是容器内部的/ bin / bash 将在其提示符内显示的名称。但主机名不容易从容器外看到。它不会出现在 docker ps 中，也不会出现在任何其他容器的/ etc / hosts 文件中。 |
|---|---|
--link = CONTAINER_NAME或 ID：ALIAS | 在运行容器时使用此选项会为新容器的/ etc / hosts 添加一个名为 ALIAS 的额外条目，该条目指向由 C ONTAINER_NAME_or_ID 标识的容器的 IP 地址。这使新容器内的进程连接到主机名称 ALIAS，而无需知道其 IP。下面将更详细地讨论--link =选项。由于 Docker 可能会在重新启动时为链接的容器分配不同的IP地址，因此 Docker 会更新收件人容器的/ etc / hosts 文件中的 ALIAS 条目。 |
--dns = IP_ADDRESS ... | 将作为域名服务器行添加的IP地址设置为容器的/etc/resolv.conf 文件。容器中的进程在遇到不在/ etc / hosts中的主机名时，将连接到端口53上的这些 IP 地址，以查找名称解析服务。 |
--dns-search=DOMAIN... | 通过在容器的/etc/resolv.conf 中写入搜索行来设置在容器内部使用裸露的不合格主机名时搜索的域名。例如，当容器进程尝试访问主机并设置搜索域 example.com 时，DNS 逻辑不仅会查找主机，还会查找 host.example.com。使用--dns-search =。如果你不想设置搜索域。 |
--dns-opt=OPTION... | 通过将选项行写入容器的/etc/resolv.conf 来设置 DNS 解析器使用的选项。有关有效选项的列表，请参阅 resolv.conf 的文档 |
关于 DNS 设置，在没有的--dns=IP_ADDRESS...，--dns-search=DOMAIN...或--dns-opt=OPTION...选项，Docker 每个容器的/etc/resolv.conf模样/etc/resolv.conf主机（其中的docker守护进程（daemon）运行）。在创建容器时/etc/resolv.conf，守护进程（daemon）从主机的原始文件中过滤掉所有本地主机 IP 地址nameserver条目。
过滤是必要的，因为主机上的所有本地主机地址都无法从容器的网络访问。在过滤之后，如果nameserver容器/etc/resolv.conf文件中没有剩余条目，守护进程将公共 Google DNS 名称服务器（8.8.8.8和8.8.4.4）添加到容器的 DNS 配置中。如果守护程序启用了 IPv6，则还将添加公共 IPv6 Google DNS 名称服务器（2001：4860：4860 :: 8888和2001：4860：4860 :: 8844）。
注意：如果您需要访问主机的本地主机解析程序，则必须修改主机上的 DNS 服务以侦听可从容器内访问的非本地主机地址。
您可能想知道主机/etc/resolv.conf文件更改时会发生什么。docker守护进程（daemon）有一个文件改变通知活跃，将监视更改到主机的 DNS 配置。
注意：文件更改通知程序依赖于 Linux 内核的 inotify 功能。由于此功能当前与覆盖文件系统驱动程序不兼容，因此使用“覆盖”的 Docker 守护程序将无法利用
/etc/resolv.conf自动更新功能。
当主机文件更改时，resolv.conf与主机匹配的所有停止的容器将立即更新为此最新的主机配置。在主机配置发生变化时运行的容器需要停下来，并且由于缺乏设施而开始采用主机更改，以确保resolv.conf在容器运行时对文件进行原子写入。如果容器resolv.conf从缺省配置启动后已经被编辑，则不会尝试替换，因为它会覆盖容器执行的更改。如果选项（--dns，，--dns-search或--dns-opt）已用于修改默认主机配置，则更新主机的更换/etc/resolv.conf也不会发生。
注意：对于
/etc/resolv.conf在 Docker 1.5.0中实现更新功能之前创建的容器：当主机文件发生更改时，这些容器将不会收到更新resolv.conf。只有使用 Docker 1.5.0或更高版本创建的容器才会使用此自动更新功能。