国产av日韩一区二区三区精品,成人性爱视频在线观看,国产,欧美,日韩,一区,www.成色av久久成人,2222eeee成人天堂

directory search
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
characters

本節(jié)中的信息說明在 Docker 默認網(wǎng)橋中配置容器 DNS。這是一個在安裝 Docker 時自動創(chuàng)建名為bridge的bridge網(wǎng)絡。

注意：通過 Docker 網(wǎng)絡功能，您可以創(chuàng)建除默認網(wǎng)橋以外的用戶定義網(wǎng)絡。有關(guān)用戶定義網(wǎng)絡中 DNS 配置的更多信息，請參閱 Docker Embedded DNS 部分。

Docker 如何為每個容器提供主機名和 DNS 配置，而不必使用內(nèi)部寫入的主機名來構(gòu)建自定義映像？它的訣竅是/etc用虛擬文件覆蓋容器內(nèi)的三個關(guān)鍵文件，以便在其中寫入新的信息。您可以通過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 接收新的配置時，在所有容器中保持最新狀態(tài)。Docker 如何在容器中維護這些文件的確切細節(jié)可以從一個 Docker 版本更改為下一個，因此您應該保留文件本身，并改為使用以下 Docker 選項。

四個不同的選項影響容器域名服務。

-h HOSTNAME或--hostname = HOSTNAME

設置容器知道自己的主機名。這寫入/ etc / hostname，寫入/ etc / hosts 作為容器的面向主機的IP地址的名稱，并且是容器內(nèi)部的/ bin / bash 將在其提示符內(nèi)顯示的名稱。但主機名不容易從容器外看到。它不會出現(xiàn)在 docker ps 中，也不會出現(xiàn)在任何其他容器的/ etc / hosts 文件中。

--link = CONTAINER_NAME或 ID：ALIAS

在運行容器時使用此選項會為新容器的/ etc / hosts 添加一個名為 ALIAS 的額外條目，該條目指向由 C ONTAINER_NAME_or_ID 標識的容器的 IP 地址。這使新容器內(nèi)的進程連接到主機名稱 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 中寫入搜索行來設置在容器內(nèi)部使用裸露的不合格主機名時搜索的域名。例如，當容器進程嘗試訪問主機并設置搜索域 example.com 時，DNS 邏輯不僅會查找主機，還會查找 host.example.com。使用--dns-search =。如果你不想設置搜索域。

--dns-opt=OPTION...

通過將選項行寫入容器的/etc/resolv.conf 來設置 DNS 解析器使用的選項。有關(guān)有效選項的列表，請參閱 resolv.conf 的文檔



關(guān)于 DNS 設置，在沒有的--dns=IP_ADDRESS...，--dns-search=DOMAIN...或--dns-opt=OPTION...選項，Docker 每個容器的/etc/resolv.conf模樣/etc/resolv.conf主機（其中的docker守護進程（daemon）運行）。在創(chuàng)建容器時/etc/resolv.conf，守護進程（daemon）從主機的原始文件中過濾掉所有本地主機 IP 地址nameserver條目。

過濾是必要的，因為主機上的所有本地主機地址都無法從容器的網(wǎng)絡訪問。在過濾之后，如果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 服務以偵聽可從容器內(nèi)訪問的非本地主機地址。

您可能想知道主機/etc/resolv.conf文件更改時會發(fā)生什么。docker守護進程（daemon）有一個文件改變通知活躍，將監(jiān)視更改到主機的 DNS 配置。

注意：文件更改通知程序依賴于 Linux 內(nèi)核的 inotify 功能。由于此功能當前與覆蓋文件系統(tǒng)驅(qū)動程序不兼容，因此使用“覆蓋”的 Docker 守護程序?qū)o法利用/etc/resolv.conf自動更新功能。

當主機文件更改時，resolv.conf與主機匹配的所有停止的容器將立即更新為此最新的主機配置。在主機配置發(fā)生變化時運行的容器需要停下來，并且由于缺乏設施而開始采用主機更改，以確保resolv.conf在容器運行時對文件進行原子寫入。如果容器resolv.conf從缺省配置啟動后已經(jīng)被編輯，則不會嘗試替換，因為它會覆蓋容器執(zhí)行的更改。如果選項（--dns，，--dns-search或--dns-opt）已用于修改默認主機配置，則更新主機的更換/etc/resolv.conf也不會發(fā)生。

注意：對于/etc/resolv.conf在 Docker 1.5.0中實現(xiàn)更新功能之前創(chuàng)建的容器：當主機文件發(fā)生更改時，這些容器將不會收到更新resolv.conf。只有使用 Docker 1.5.0或更高版本創(chuàng)建的容器才會使用此自動更新功能。

Previous article： Next article：