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
?
This document uses PHP Chinese website manual Release
characters
本文檔適用于那些希望指定自定義選項的運行自己的公證服務
概述
公證服務器需要配置文件，并且必須使用命令行中的-config選項指定配置文件的路徑。
公證服務器還允許您增加/減少日志記錄級別，而無需重新啟動。
下面是一個完整的服務器配置文件示例；請單擊頂級JSON鍵，了解與該鍵對應的配置部分的更多信息：
{ "server": {
"http_addr": ":4443",
"tls_key_file": "./fixtures/notary-server.key",
"tls_cert_file": "./fixtures/notary-server.crt"
},
"trust_service": {
"type": "remote",
"hostname": "notarysigner",
"port": "7899",
"key_algorithm": "ecdsa",
"tls_ca_file": "./fixtures/root-ca.crt",
"tls_client_cert": "./fixtures/notary-server.crt",
"tls_client_key": "./fixtures/notary-server.key"
},
"storage": {
"backend": "mysql",
"db_url": "user:pass@tcp(notarymysql:3306)/databasename?parseTime=true"
},
"auth": {
"type": "token",
"options": {
"realm": "https://auth.docker.io/token",
"service": "notary-server",
"issuer": "auth.docker.io",
"rootcertbundle": "/path/to/auth.docker.io/cert"
}
},
"logging": { "level": "debug" },
"reporting": { "bugsnag": {
"api_key": "c9d60ae4c7e70c4b6c4ebd3e8056d2b8",
"release_stage": "production" }
},
"caching": { "max_age": {
"current_metadata": 300,
"consistent_metadata": 31536000,
}
},
"repositories": { "gun_prefixes": ["docker.io/", "my-own-registry.com/"] }}服務器部分（必填）
例子：
"server": { "http_addr": ":4443", "tls_key_file": "./fixtures/notary-server.key", "tls_cert_file": "./fixtures/notary-server.crt"}參數(shù) | 需要 | 描述 |
|---|---|---|
http_addr | 是 | 要監(jiān)聽的TCP地址（IP和端口）。例如：“：4443”表示監(jiān)聽所有IP上的端口4443（因此所有接口，如運行ifconfig時列出的那些接口）“127.0.0.1:4443”表示只偵聽本地主機上的端口4443。這意味著除了本地服務器之外，服務器將不可訪問（通過SSH隧道或僅在本地終端上） |
tls_key_file | 否 | 私鑰用于HTTPS的路徑。必須與tls_cert_file一起提供，或根本不提供。如果沒有提供，服務器將使用HTTP而不是HTTPS。該路徑相對于配置文件的目錄。 |
tls_cert_file | 否 | 用于HTTPS的證書路徑。必須與tls_key_file一起提供，或根本不提供。如果沒有提供，服務器將使用HTTP而不是HTTPS。該路徑相對于配置文件的目錄。 |
":4443"意味著在所有IP上的端口4443上偵聽（因此所有接口，例如運行時列出的接口ifconfig）
"127.0.0.1:4443"表示僅在本地主機上偵聽端口4443。這意味著除了本地服務器之外，服務器將不可訪問（通過SSH隧道或僅在本地終端上）
`tls_key_file` no The path to the private key to use for HTTPS. Must be provided together with `tls_cert_file`, or not at all. If neither are provided, the server will use HTTP instead of HTTPS. The path is relative to the directory of the configuration file. `tls_cert_file` no The path to the certificate to use for HTTPS. Must be provided together with `tls_key_file`, or not at all. If neither are provided, the server will use HTTP instead of HTTPS. The path is relative to the directory of the configuration file.
trust_service部分（必填）
本節(jié)配置遠程信任服務，如公證人簽字人或本地內(nèi)存中的ED25519信任服務。
遠程信任服務示例：
"trust_service": { "type": "remote", "hostname": "notarysigner", "port": "7899", "key_algorithm": "ecdsa", "tls_ca_file": "./fixtures/root-ca.crt", "tls_client_cert": "./fixtures/notary-server.crt", "tls_client_key": "./fixtures/notary-server.key"}本地信托服務示例：
"trust_service": { "type": "local"}參數(shù) | 是否需要 | 描述 |
|---|---|---|
type | 是 | 必須是“遠程”或“本地” |
hostname | 若為remote則是 | 遠程信任服務的主機名 |
key_algorithm | 若為remote則是 | 遠程信任服務的GRPC端口 |
key_algorithm | 若為remote則是 | 用于生成存儲在簽名服務上的密鑰的算法。有效值是“ecdsa”，“rsa”和“ed25519”。 |
tls_ca_file | 否 | 簽署遠程服務的TLS證書的根CA的路徑。如果所述根CA不在系統(tǒng)的默認信任根中，則必須提供此參數(shù)。該路徑相對于配置文件的目錄。 |
tls_client_key | 否 | 私鑰用于TLS相互認證的路徑。這必須與tls_client_cert一起提供，或根本不提供。該路徑相對于配置文件的目錄。 |
tls_client_cert | 否 | 證書用于TLS相互身份驗證的路徑。這必須與tls_client_key一起提供或根本不提供。該路徑相對于配置文件的目錄。 |
存儲部分（必填）
存儲部分指定服務器應該使用哪個存儲后端來存儲TUF元數(shù)據(jù)。只支持MySQL或內(nèi)存存儲。
DB存儲示例：
"storage": { "backend": "mysql", "db_url": "user:pass@tcp(notarymysql:3306)/databasename?parseTime=true"}參數(shù) | 是否需要 | 描述 |
|---|---|---|
backend | 是 | 必須是“mysql”或“內(nèi)存”。如果選擇“內(nèi)存”，則會忽略db_url。 |
db_url | 是的，如果不是內(nèi)存 | 用于訪問數(shù)據(jù)庫的數(shù)據(jù)源名稱。（注意：請包含parseTime = true作為DSN的一部分） |
身份驗證部分（可選）
本節(jié)指定服務器的身份驗證選項。目前，我們只支持令牌身份驗證。
例子：
"auth": { "type": "token", "options": { "realm": "https://auth.docker.io", "service": "notary-server", "issuer": "auth.docker.io", "rootcertbundle": "/path/to/auth.docker.io/cert" }}注意，整個部分是可選的。但是，如果您想要對服務器進行身份驗證，那么您需要下面所需的參數(shù)來配置它。
令牌身份驗證：
這是Docker注冊表第2版使用的相同身份驗證的實現(xiàn)。（基于JWT令牌的認證后登錄。）
參數(shù) | 是否需要 | 描述 |
|---|---|---|
類型 | 是 | 必須是“令牌”; 所有其他值將導致無認證（其余參數(shù)將被忽略） |
選項 | 是 | 令牌認證的選項。請參閱注冊表令牌配置文檔以獲取參數(shù)詳細信息。 |
緩存部分（可選）
例子：
"caching": { "max_age": { "current_metadata": 300, "consistent_metadata": 31536000, }}參數(shù) | 是否需要 | 描述 |
|---|---|---|
MAX_AGE | 否 | 緩存服務通過角色的校驗和緩存角色的最新元數(shù)據(jù)和元數(shù)據(jù)的最大時間（以秒為單位）。該值將在GET-ting元數(shù)據(jù)的緩存控制標頭上設置。請注意，must-revalidate也在當前元數(shù)據(jù)的緩存控制標頭上設置，因為無論何時將新的元數(shù)據(jù)登錄到回購中，當前的元數(shù)據(jù)都可能會更改。一致的元數(shù)據(jù)不應該改變，盡管可能會被刪除，所以最大年齡可能會更高。 |
存儲庫部分（可選）
例子：
"repositories": { "gun_prefixes": ["docker.io/", "my-own-registry.com/"]}參數(shù) | 是否需要 | 描述 |
|---|---|---|
gun_prefixes | 否 | 此服務器將接受的GUN前綴列表。以任何其他前綴開頭的映像上的POST操作將被400拒絕，并且GET / DELETE操作將被404拒絕。 |
熱日志記錄級別重新加載
目前我們還不支持完全重新加載公證配置文件。我們現(xiàn)在支持的是：
通過信令提高日志記錄級別
SIGUSR1
通過信令降低日志記錄級別
SIGUSR2
例子：
增加日志記錄級別
$ kill -s SIGUSR1 PID or $ docker exec -i CONTAINER_ID kill -s SIGUSR1 PID
減少日志記錄級別
$ kill -s SIGUSR2 PID or $ docker exec -i CONTAINER_ID kill -s SIGUSR2 PID
如果您使用某種包裝器啟動腳本或某些類型的容器運行容器，則PID是進程IDnotary-server，并且可能不是PID 1進程。
你可以得到notary-server通過的PID
$ docker exec CONTAINER_ID ps aux or $ ps aux | grep "notary-server -config" | grep -v "grep"
相關信息
公證簽字人配置文件
公證服務器和簽名者常用的配置部分