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
?
This document uses PHP Chinese website manual Release
characters
默認(rèn)情況下，Docker通過(guò)一個(gè)非聯(lián)網(wǎng)的Unix套接字運(yùn)行。它還可以選擇使用HTTP套接字進(jìn)行通信。
如果您需要以安全的方式通過(guò)網(wǎng)絡(luò)聯(lián)系到Docker，則可以通過(guò)指定tlsverify旗幟和指點(diǎn)碼頭tlscacert標(biāo)記為可信CA證書(shū)。
在守護(hù)進(jìn)程模式中，它將只允許來(lái)自由該CA簽名的證書(shū)驗(yàn)證的客戶(hù)端的連接。在客戶(hù)端模式下，它將只連接到由該CA簽名的證書(shū)的服務(wù)器。
警告使用TLS和管理CA是一個(gè)高級(jí)主題。在生產(chǎn)中使用OpenSSL、x 509和TLS之前，請(qǐng)熟悉它。警告這些TLS命令將只在Linux上生成一組有效的證書(shū)。MacOS附帶的OpenSSL版本與Docker所需的證書(shū)不兼容。
使用OpenSSL創(chuàng)建CA、服務(wù)器和客戶(hù)端密鑰
注*替換所有的實(shí)例
$HOST在下面的示例中，使用Docker守護(hù)進(jìn)程主機(jī)的DNS名稱(chēng)。
首先，在Docker守護(hù)進(jìn)程的主機(jī)，生成CA私鑰和公鑰：
$ openssl genrsa -aes256 -out ca-key.pem 4096Generating RSA private key, 4096 bit long modulus............................................................................................................................................................................................++........++e is 65537 (0x10001)Enter pass phrase for ca-key.pem:Verifying - Enter pass phrase for ca-key.pem:$ openssl req -new -x509 -days 365 -key ca-key.pem -sha256 -out ca.pem Enter pass phrase for ca-key.pem:You are about to be asked to enter information that will be incorporated into your certificate request.What you are about to enter is what is called a Distinguished Name or a DN.There are quite a few fields but you can leave some blank For some fields there will be a default value,If you enter '.', the field will be left blank.-----Country Name (2 letter code) [AU]:State or Province Name (full name) [Some-State]:Queensland Locality Name (eg, city) []:Brisbane Organization Name (eg, company) [Internet Widgits Pty Ltd]:Docker Inc Organizational Unit Name (eg, section) []:Sales Common Name (e.g. server FQDN or YOUR name) []:$HOST Email Address []:Sven@home.org.au
現(xiàn)在我們有一個(gè)CA，您可以創(chuàng)建一個(gè)服務(wù)器密鑰和證書(shū)簽名請(qǐng)求（CSR）。確?！癈ommon Name”（即服務(wù)器FQDN或您的姓名）與您將用于連接到Docker的主機(jī)名匹配：
注*替換所有的實(shí)例
$HOST在下面的示例中，使用Docker守護(hù)進(jìn)程主機(jī)的DNS名稱(chēng)。
$ openssl genrsa -out server-key.pem 4096Generating RSA private key, 4096 bit long modulus.....................................................................++.................................................................................................++e is 65537 (0x10001)$ openssl req -subj "/CN=$HOST" -sha256 -new -key server-key.pem -out server.csr
接下來(lái)，我們將使用我們的CA簽署公鑰：
由于TLS連接可以通過(guò)IP地址和DNS名稱(chēng)進(jìn)行，所以在創(chuàng)建證書(shū)時(shí)需要指定IP地址。例如，若要允許連接使用10.10.10.20和127.0.0.1*
$ echo subjectAltName = DNS:$HOST,IP:10.10.10.20,IP:127.0.0.1 > extfile.cnf
將Docker守護(hù)進(jìn)程密鑰的擴(kuò)展使用屬性設(shè)置為僅用于服務(wù)器身份驗(yàn)證：
$ echo extendedKeyUsage = serverAuth > extfile.cnf
現(xiàn)在，生成密鑰：
$ openssl x509 -req -days 365 -sha256 -in server.csr -CA ca.pem -CAkey ca-key.pem \ -CAcreateserial -out server-cert.pem -extfile extfile.cnf Signature ok subject=/CN=your.host.com Getting CA Private Key Enter pass phrase for ca-key.pem:
授權(quán)插件提供更細(xì)粒度的控制，以補(bǔ)充來(lái)自互TLS的身份驗(yàn)證。除了上述文檔中描述的其他信息之外，運(yùn)行在Docker守護(hù)進(jìn)程上的授權(quán)插件還接收連接Docker客戶(hù)端的證書(shū)信息。
對(duì)于客戶(hù)端身份驗(yàn)證，創(chuàng)建客戶(hù)端密鑰和證書(shū)簽名請(qǐng)求：
注：為了簡(jiǎn)化接下來(lái)的幾個(gè)步驟，您也可以在Docker守護(hù)進(jìn)程的主機(jī)上執(zhí)行這個(gè)步驟。
$ openssl genrsa -out key.pem 4096Generating RSA private key, 4096 bit long modulus.........................................................++................++e is 65537 (0x10001)$ openssl req -subj '/CN=client' -new -key key.pem -out client.csr
要使密鑰適合客戶(hù)端身份驗(yàn)證，請(qǐng)創(chuàng)建一個(gè)擴(kuò)展名配置文件：
$ echo extendedKeyUsage = clientAuth > extfile.cnf
現(xiàn)在簽署私鑰：
$ openssl x509 -req -days 365 -sha256 -in client.csr -CA ca.pem -CAkey ca-key.pem \ -CAcreateserial -out cert.pem -extfile extfile.cnf Signature ok subject=/CN=client Getting CA Private Key Enter pass phrase for ca-key.pem:
生成后cert.pem和server-cert.pem您可以安全地刪除兩個(gè)證書(shū)簽名請(qǐng)求：
$ rm -v client.csr server.csr
在默認(rèn)情況下umask022歲的時(shí)候，你的秘密鑰匙世界可讀性也可以為你和你的團(tuán)隊(duì)寫(xiě)。
為了保護(hù)您的密鑰不受意外損壞，您需要?jiǎng)h除它們的寫(xiě)權(quán)限。若要使它們僅供您閱讀，請(qǐng)按以下方式更改文件模式：
$ chmod -v 0400 ca-key.pem key.pem server-key.pem
證書(shū)可以具有世界可讀性，但您可能希望刪除寫(xiě)入訪問(wèn)，以防止意外損壞：
$ chmod -v 0444 ca.pem server-cert.pem cert.pem
現(xiàn)在，您可以讓Docker守護(hù)進(jìn)程只接受來(lái)自客戶(hù)端的連接，這些客戶(hù)端提供了我們的CA信任的證書(shū)：
$ dockerd --tlsverify --tlscacert=ca.pem --tlscert=server-cert.pem --tlskey=server-key.pem \ -H=0.0.0.0:2376
要連接到Docker并驗(yàn)證其證書(shū)，現(xiàn)在需要提供客戶(hù)端密鑰、證書(shū)和可信CA：
注此步驟應(yīng)在您的Docker客戶(hù)端計(jì)算機(jī)上運(yùn)行。因此，您需要將CA證書(shū)、服務(wù)器證書(shū)和客戶(hù)端證書(shū)復(fù)制到該計(jì)算機(jī)。注*替換所有的實(shí)例
$HOST在下面的示例中，使用Docker守護(hù)進(jìn)程主機(jī)的DNS名稱(chēng)。
$ docker --tlsverify --tlscacert=ca.pem --tlscert=cert.pem --tlskey=key.pem \ -H=$HOST:2376 version
注意：通過(guò)TLS的Docker應(yīng)該在TCP端口2376上運(yùn)行。警告：如上例所示，當(dāng)您使用證書(shū)身份驗(yàn)證時(shí)，不必
docker使用sudo或docker組運(yùn)行客戶(hù)端。這意味著任何擁有密鑰的人都可以給你的Docker守護(hù)進(jìn)程提供任何指令，讓他們可以訪問(wèn)托管守護(hù)進(jìn)程的機(jī)器。保護(hù)這些密鑰，就像你使用root密碼一樣！
默認(rèn)安全
如果您想默認(rèn)保護(hù)您的Docker客戶(hù)端連接，您可以將文件移動(dòng)到.docker您的主目錄中的目錄 - 并設(shè)置DOCKER_HOST和DOCKER_TLS_VERIFY變量（而不是傳遞-H=tcp://$HOST:2376和--tlsverify每次調(diào)用）。
$ mkdir -pv ~/.docker
$ cp -v {ca,cert,key}.pem ~/.docker
$ export DOCKER_HOST=tcp://$HOST:2376 DOCKER_TLS_VERIFY=1默認(rèn)情況下，Docker現(xiàn)在將安全地連接：
$ docker ps
其他模式
如果您不想擁有完全的雙向身份驗(yàn)證，可以通過(guò)混合標(biāo)志在其他各種模式下運(yùn)行Docker。
守護(hù)進(jìn)程模式
tlsverify，tlscacert，tlscert，tlskey集：驗(yàn)證客戶(hù)端
tls，tlscert，tlskey：不要驗(yàn)證客戶(hù)端
客戶(hù)模式
tls*基于公共/默認(rèn)CA池的服務(wù)器身份驗(yàn)證
tlsverify，tlscacert：根據(jù)給定的CA驗(yàn)證服務(wù)器
tls，tlscert，tlskey：以驗(yàn)證客戶(hù)端證書(shū)，不驗(yàn)證服務(wù)器基于給定CA
tlsverify，tlscacert，tlscert，tlskey：以驗(yàn)證客戶(hù)端證書(shū)并認(rèn)證服務(wù)器基于給定CA
如果找到，客戶(hù)端將發(fā)送其客戶(hù)端證書(shū)，因此您只需將鑰匙放入~/.docker/{ca,cert,key}.pem?；蛘撸绻雽⒚荑€存儲(chǔ)在其他位置，則可以使用環(huán)境變量指定該位置DOCKER_CERT_PATH。
$ export DOCKER_CERT_PATH=~/.docker/zone1/$ docker --tlsverify ps
使用curl
使用curl要發(fā)出測(cè)試API請(qǐng)求，需要使用三個(gè)額外的命令行標(biāo)志：
$ curl https://$HOST:2376/images/json \ --cert ~/.docker/cert.pem \ --key ~/.docker/key.pem \ --cacert ~/.docker/ca.pem
相關(guān)信息
使用證書(shū)進(jìn)行存儲(chǔ)庫(kù)客戶(hù)端驗(yàn)證
使用可信映像