ディレクトリ 検索
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
テキスト

本文档适用于那些希望指定自定义选项的运行自己的公证服务

概述

公证服务器需要配置文件,并且必须使用命令行中的-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"}

参数

需要

描述

http_addr

要监听的TCP地址(IP和端口)。例如:“:4443”表示监听所有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部分(必填)

本节配置远程信任服务,如公证人签字人或本地内存中的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"}

参数

是否需要

描述

type

必须是“远程”或“本地”

hostname

若为remote则是

远程信任服务的主机名

key_algorithm

若为remote则是

远程信任服务的GRPC端口

key_algorithm

若为remote则是

用于生成存储在签名服务上的密钥的算法。有效值是“ecdsa”,“rsa”和“ed25519”。

tls_ca_file

签署远程服务的TLS证书的根CA的路径。如果所述根CA不在系统的默认信任根中,则必须提供此参数。该路径相对于配置文件的目录。

tls_client_key

私钥用于TLS相互认证的路径。这必须与tls_client_cert一起提供,或根本不提供。该路径相对于配置文件的目录。

tls_client_cert

证书用于TLS相互身份验证的路径。这必须与tls_client_key一起提供或根本不提供。该路径相对于配置文件的目录。

存储部分(必填)

存储部分指定服务器应该使用哪个存储后端来存储TUF元数据。只支持MySQL或内存存储。

DB存储示例:

"storage": {  "backend": "mysql",  "db_url": "user:pass@tcp(notarymysql:3306)/databasename?parseTime=true"}

参数

是否需要

描述

backend

必须是“mysql”或“内存”。如果选择“内存”,则会忽略db_url。

db_url

是的,如果不是内存

用于访问数据库的数据源名称。(注意:请包含parseTime = true作为DSN的一部分)

身份验证部分(可选)

本节指定服务器的身份验证选项。目前,我们只支持令牌身份验证。

例子:

"auth": {  "type": "token",  "options": {    "realm": "https://auth.docker.io",    "service": "notary-server",    "issuer": "auth.docker.io",    "rootcertbundle": "/path/to/auth.docker.io/cert"  }}

注意,整个部分是可选的。但是,如果您想要对服务器进行身份验证,那么您需要下面所需的参数来配置它。

令牌身份验证:

这是Docker注册表第2版使用的相同身份验证的实现。(基于JWT令牌的认证后登录。)

参数

是否需要

描述

类型

必须是“令牌”; 所有其他值将导致无认证(其余参数将被忽略)

选项

令牌认证的选项。请参阅注册表令牌配置文档以获取参数详细信息。

缓存部分(可选)

例子:

"caching": {  "max_age": {    "current_metadata": 300,    "consistent_metadata": 31536000,  }}

参数

是否需要

描述

MAX_AGE

缓存服务通过角色的校验和缓存角色的最新元数据和元数据的最大时间(以秒为单位)。该值将在GET-ting元数据的缓存控制标头上设置。请注意,must-revalidate也在当前元数据的缓存控制标头上设置,因为无论何时将新的元数据登录到回购中,当前的元数据都可能会更改。一致的元数据不应该改变,尽管可能会被删除,所以最大年龄可能会更高。

存储库部分(可选)

例子:

"repositories": {  "gun_prefixes": ["docker.io/", "my-own-registry.com/"]}

参数

是否需要

描述

gun_prefixes

此服务器将接受的GUN前缀列表。以任何其他前缀开头的映像上的POST操作将被400拒绝,并且GET / DELETE操作将被404拒绝。

热日志记录级别重新加载

目前我们还不支持完全重新加载公证配置文件。我们现在支持的是:

  • 通过信令提高日志记录级别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"

相关信息

  • 公证签字人配置文件

  • 公证服务器和签名者常用的配置部分

前の記事: 次の記事: