亚洲国产日韩欧美一区二区三区,精品亚洲国产成人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

日志驅(qū)動程序插件

本文檔介紹了Docker的日志驅(qū)動程序插件。

記錄驅(qū)動程序使用戶能夠?qū)⑷萜魅罩巨D(zhuǎn)發(fā)到其他服務(wù)進(jìn)行處理。Docker包含幾個(gè)日志驅(qū)動程序作為內(nèi)置函數(shù),但不能希望通過內(nèi)置驅(qū)動程序支持所有的使用情況。插件允許Docker支持廣泛的日志記錄服務(wù),而無需在主要Docker代碼庫中為這些服務(wù)嵌入客戶端庫。有關(guān)更多信息,請參閱插件文檔。

創(chuàng)建日志插件

日志插件的主界面使用與其他插件類型使用的相同的JSON + HTTP RPC協(xié)議。請參閱示例插件以獲取日志插件的參考實(shí)現(xiàn)。這個(gè)例子包裝了內(nèi)置的jsonfilelog日志驅(qū)動程序。

LogDriver協(xié)議

記錄插件必須在插件激活期間注冊為LogDriver。一旦激活的用戶可以指定插件作為日志驅(qū)動程序。

有兩個(gè)日志插件必須實(shí)現(xiàn)的HTTP端點(diǎn):

/LogDriver.StartLogging

向插件發(fā)信號通知容器正在啟動,插件應(yīng)該開始接收日志。

日志將通過請求中定義的文件進(jìn)行流式傳輸。在Linux上,這個(gè)文件是一個(gè)FIFO。Windows上目前不支持日志記錄插件。

請求*

{"File": "/path/to/file/stream","Info": {"ContainerID": "123456"}}

File是需要使用的日志流的路徑。每次調(diào)用都StartLogging應(yīng)該提供不同的文件路徑,即使它是插件已經(jīng)收到日志的容器。該文件由docker用隨機(jī)生成的名稱創(chuàng)建。

Info是有關(guān)正在記錄的容器的詳細(xì)信息。這是相當(dāng)自由的形式,但是由以下結(jié)構(gòu)定義來定義:

type Info struct {
	Config              map[string]string
	ContainerID         string
	ContainerName       string
	ContainerEntrypoint string
	ContainerArgs       []string
	ContainerImageID    string
	ContainerImageName  string
	ContainerCreated    time.Time
	ContainerEnv        []string
	ContainerLabels     map[string]string
	LogPath             string
	DaemonName          string}

ContainerID 將始終提供此結(jié)構(gòu),但其他字段可能為空或缺失。

響應(yīng)

{"Err": ""}

如果在此請求期間發(fā)生錯(cuò)誤,請將錯(cuò)誤消息添加到Err響應(yīng)中的字段。如果沒有錯(cuò)誤,那么你可以發(fā)送一個(gè)空的響應(yīng)({})或一個(gè)空的值的Err字段。

此時(shí)驅(qū)動程序應(yīng)該使用傳入文件中的日志消息。如果消息未被使用,它可能會導(dǎo)致容器在嘗試寫入其stdio流時(shí)被阻塞。

日志流消息被編碼為協(xié)議緩沖區(qū)。protobuf定義在docker倉庫中。

由于協(xié)議緩沖區(qū)不是自分隔的,所以必須使用以下流格式從流中解碼它們:

[size][message]

在哪里size是一個(gè)4字節(jié)的大端二進(jìn)制編碼uint32。size在這種情況下定義下一個(gè)消息的大小。message是實(shí)際的日志條目。

流編碼器/解碼器的參考golang實(shí)現(xiàn)可以在這里找到

/LogDriver.StopLogging

指示插件停止從定義的文件中收集日志。一旦收到響應(yīng),該文件將被Docker刪除。在回應(yīng)此請求之前,您必須確保收集流上的所有日志,否則可能會丟失日志數(shù)據(jù)。

此端點(diǎn)上的請求并不意味著該容器僅在已停止的情況下被移除。

請求:

{"File": "/path/to/file/stream"}

響應(yīng):

{"Err": ""}

如果在此請求期間發(fā)生錯(cuò)誤,請將錯(cuò)誤消息添加到Err響應(yīng)中的字段。如果沒有錯(cuò)誤,那么你可以發(fā)送一個(gè)空的響應(yīng)({})或一個(gè)空的值的Err字段。

可選端點(diǎn)

日志記錄插件可以實(shí)現(xiàn)兩個(gè)額外的日志記錄端點(diǎn):

/LogDriver.Capabilities

定義日志驅(qū)動程序的功能。您必須為Docker實(shí)現(xiàn)此端點(diǎn)才能利用任何已定義的功能。

請求:

{}

響應(yīng)

{"ReadLogs": true}

支助能力:

  • ReadLogs - 這告訴Docker該插件能夠?qū)⑷罩咀x回客戶端。報(bào)告他們支持的插件ReadLogs必須實(shí)現(xiàn)/LogDriver.ReadLogs端點(diǎn)/LogDriver.ReadLogs將日志讀回客戶端。這在docker logs <container>被調(diào)用時(shí)使用。為了讓Docker使用這個(gè)端點(diǎn),插件必須在/LogDriver.Capabilities被調(diào)用時(shí)指定多少。

請求

"ReadConfig": {}, "Info": { "ContainerID": "123456" } }

ReadConfig是閱讀選項(xiàng)列表,它定義了一個(gè)具有以下golang結(jié)構(gòu):類型ReadConfig結(jié)構(gòu){由于尾了time.time int跟隨bool}

  • Since定義應(yīng)該發(fā)送的最舊日志。

  • Tail定義要讀取的行數(shù)(例如,像命令tail -n 10

  • Follow 表示客戶希望保持連接狀態(tài),以便在讀取現(xiàn)有日志后收到新的日志消息。

Info是在中定義的相同類型/LogDriver.StartLogging。它應(yīng)該用于確定要讀取的日志集合。

響應(yīng):

響應(yīng)應(yīng)該是編碼的日志消息,使用與插件從Docker消耗的消息相同的格式。

Previous article: Next article: