亚洲国产日韩欧美一区二区三区,精品亚洲国产成人av在线,国产99视频精品免视看7,99国产精品久久久久久久成人热,欧美日韩亚洲国产综合乱

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默認(rèn)網(wǎng)橋中的容器通信。這是一個在安裝Docker時自動創(chuàng)建的bridge網(wǎng)絡(luò)bridge

注意:通過Docker網(wǎng)絡(luò)功能,您可以創(chuàng)建除默認(rèn)網(wǎng)橋以外的用戶定義網(wǎng)絡(luò)。

與外界溝通

一個容器是否可以與世界交流受兩個因素控制。第一個因素是主機是否轉(zhuǎn)發(fā)其IP數(shù)據(jù)包。其次是主機是否iptables允許這種特定的連接。

IP數(shù)據(jù)包轉(zhuǎn)發(fā)由ip_forward系統(tǒng)參數(shù)管理。如果此參數(shù)是數(shù)據(jù)包,則只能在容器之間傳遞數(shù)據(jù)包1。通常你會簡單地離開了碼頭工人服務(wù)器的默認(rèn)設(shè)置--ip-forward=true和碼頭工人會去設(shè)置ip_forward,以1在服務(wù)器啟動時你。如果您設(shè)置--ip-forward=false并且您的系統(tǒng)內(nèi)核已啟用該--ip-forward=false選項,則該選項不起作用。要檢查內(nèi)核上的設(shè)置或手動打開它:

  $ sysctl net.ipv4.conf.all.forwarding

  net.ipv4.conf.all.forwarding = 0

  $ sysctl net.ipv4.conf.all.forwarding=1

  $ sysctl net.ipv4.conf.all.forwarding

  net.ipv4.conf.all.forwarding = 1

注意:此設(shè)置不會影響使用主機網(wǎng)絡(luò)堆棧(--network=host)的容器。

許多使用Docker的人都希望ip_forward開啟,至少可以在容器和更廣泛的世界之間進(jìn)行通信。如果您處于多個橋接設(shè)置中,也可能需要進(jìn)行集裝箱間通信。

如果您設(shè)置--iptables=false守護進(jìn)程啟動時,Docker將永遠(yuǎn)不會更改您的系統(tǒng)規(guī)則iptables。否則,Docker服務(wù)器會將轉(zhuǎn)發(fā)規(guī)則附加到DOCKER過濾器鏈中。

Docker將刷新任何預(yù)先存在的規(guī)則,從DOCKERDOCKER-ISOLATION過濾器鏈,如果存在的話。出于這個原因,需要在Docker啟動后添加任何需要進(jìn)一步限制對容器訪問的規(guī)則。

Docker的轉(zhuǎn)發(fā)規(guī)則默認(rèn)允許所有外部源IP。要僅允許特定的IP或網(wǎng)絡(luò)訪問容器,請在DOCKER過濾器鏈的頂部插入否定規(guī)則。例如,要限制外部訪問,以便只有源IP 8.8.8.8才能訪問容器,可以添加以下規(guī)則:

$ iptables -I DOCKER -i ext_if ! -s 8.8.8.8 -j DROP

其中ext_if是提供到主機的外部連接的接口的名稱。

容器之間的通信

兩個容器是否可以通信在操作系統(tǒng)級別由兩個因素決定。

  • 網(wǎng)絡(luò)拓?fù)涫欠襁B接了容器的網(wǎng)絡(luò)接口?默認(rèn)情況下,Docker會將所有容器附加到一個docker0橋,為數(shù)據(jù)包之間的傳輸提供路徑。有關(guān)其他可能的拓?fù)洌垍㈤啽疚臋n的后面部分。

  • 你的iptables是否允許這個特定的連接?如果您設(shè)置--iptables=false守護進(jìn)程啟動時,Docker將永遠(yuǎn)不會更改您的系統(tǒng)規(guī)則iptables。否則,如果保留缺省值,則Docker服務(wù)器將FORWARD使用一攬子ACCEPT策略向該鏈添加默認(rèn)規(guī)則--icc=true,否則會將該策略設(shè)置為DROP如果--icc=false。

這是一個戰(zhàn)略性問題,是否要保留--icc=true或改變,--icc=false以便iptables保護其他容器和主要主機不受任何受到攻擊的容器探測或訪問的端口的限制。

如果您選擇最安全的設(shè)置--icc=false,那么在您希望他們提供對方服務(wù)的情況下,容器如何通信?答案就是--link=CONTAINER_NAME_or_ID:ALIAS選項,因為它對名稱服務(wù)的影響,在前一節(jié)中提到了這個選項。如果Docker守護進(jìn)程正在運行--icc=false并且--iptables=true隨后運行,當(dāng)它看到docker run使用該--link=選項調(diào)用時,Docker服務(wù)器將插入一對iptables ACCEPT規(guī)則,以便新容器可以連接到其他容器公開的端口 - 它提到的端口它的EXPOSEDockerfile

CONTAINER_NAME值的--link=必須是自動分配的Docker的名字一樣stupefied_pare,或者你用指定的名稱--name=,當(dāng)你跑了docker run。它不能是主機名,Docker在該--link=選項的上下文中不會識別。

您可以在Docker主機上運行Fiptables命令,以查看該ORWARD鏈?zhǔn)欠窬哂心J(rèn)策略為ACCEPTDROP

# When --icc=false, you should see a DROP rule:$ sudo iptables -L -n...Chain FORWARD (policy ACCEPT)target     prot opt source               destination
DOCKER     all  --  0.0.0.0/0            0.0.0.0/0DROP       all  --  0.0.0.0/0            0.0.0.0/0...# When a --link= has been created under --icc=false,# you should see port-specific ACCEPT rules overriding
# the subsequent DROP policy for all other packets:$ sudo iptables -L -n...Chain FORWARD (policy ACCEPT)target     prot opt source               destination
DOCKER     all  --  0.0.0.0/0            0.0.0.0/0DROP       all  --  0.0.0.0/0            0.0.0.0/0Chain DOCKER (1 references)target     prot opt source               destination
ACCEPT     tcp  --  172.17.0.2           172.17.0.3           tcp spt:80ACCEPT     tcp  --  172.17.0.3           172.17.0.2           tcp dpt:80

注意:Docker非常小心它的主機范圍iptables規(guī)則完全將容器暴露給彼此的原始IP地址,因此從一個容器到另一個容器的連接總是應(yīng)該來自第一個容器自己的IP地址。

主機間的容器通信

出于安全原因,Docker配置iptables規(guī)則以防止容器在Linux主機上從主機外部轉(zhuǎn)發(fā)流量。Docker將FORWARD鏈的默認(rèn)策略設(shè)置為DROP。

要覆蓋此默認(rèn)行為,您可以手動更改默認(rèn)策略:

$ sudo iptables -P FORWARD ACCEPT

iptables當(dāng)系統(tǒng)重新啟動設(shè)置都將丟失。如果您希望更改是永久的,請參閱您的Linux發(fā)行版的文檔。

注意:在Docker 1.12及更早版本中,默認(rèn)FORWARD鏈策略是ACCEPT。當(dāng)您升級到Docker 1.13或更高版本時,此默認(rèn)值會自動為您更改。如果您以前的工作配置包含跨多個主機的多個容器,則此更改可能會導(dǎo)致現(xiàn)有設(shè)置停止工作,如果您不介入。

為什么你需要將默認(rèn)值更改DROPACCEPT

假設(shè)你有兩臺主機,每臺主機都有以下配置

host1: eth0/192.168.7.1, docker0/172.17.0.0/16host2: eth0/192.168.8.1, docker0/172.18.0.0/16

如果運行在容器host1需要與容器直接溝通的能力host2,你需要從路線host1host2。路由存在后,host2需要能夠接受去往其運行容器的數(shù)據(jù)包,并將其轉(zhuǎn)發(fā)。設(shè)置政策來ACCEPT完成這一點。

Previous article: Next article: