目錄 搜尋
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
文字

日志驱动程序插件

本文档介绍了Docker的日志驱动程序插件。

记录驱动程序使用户能够将容器日志转发到其他服务进行处理。Docker包含几个日志驱动程序作为内置函数,但不能希望通过内置驱动程序支持所有的使用情况。插件允许Docker支持广泛的日志记录服务,而无需在主要Docker代码库中为这些服务嵌入客户端库。有关更多信息,请参阅插件文档。

创建日志插件

日志插件的主界面使用与其他插件类型使用的相同的JSON + HTTP RPC协议。请参阅示例插件以获取日志插件的参考实现。这个例子包装了内置的jsonfilelog日志驱动程序。

LogDriver协议

记录插件必须在插件激活期间注册为LogDriver。一旦激活的用户可以指定插件作为日志驱动程序。

有两个日志插件必须实现的HTTP端点:

/LogDriver.StartLogging

向插件发信号通知容器正在启动,插件应该开始接收日志。

日志将通过请求中定义的文件进行流式传输。在Linux上,这个文件是一个FIFO。Windows上目前不支持日志记录插件。

请求*

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

File是需要使用的日志流的路径。每次调用都StartLogging应该提供不同的文件路径,即使它是插件已经收到日志的容器。该文件由docker用随机生成的名称创建。

Info是有关正在记录的容器的详细信息。这是相当自由的形式,但是由以下结构定义来定义:

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 将始终提供此结构,但其他字段可能为空或缺失。

响应

{"Err": ""}

如果在此请求期间发生错误,请将错误消息添加到Err响应中的字段。如果没有错误,那么你可以发送一个空的响应({})或一个空的值的Err字段。

此时驱动程序应该使用传入文件中的日志消息。如果消息未被使用,它可能会导致容器在尝试写入其stdio流时被阻塞。

日志流消息被编码为协议缓冲区。protobuf定义在docker仓库中。

由于协议缓冲区不是自分隔的,所以必须使用以下流格式从流中解码它们:

[size][message]

在哪里size是一个4字节的大端二进制编码uint32。size在这种情况下定义下一个消息的大小。message是实际的日志条目。

流编码器/解码器的参考golang实现可以在这里找到

/LogDriver.StopLogging

指示插件停止从定义的文件中收集日志。一旦收到响应,该文件将被Docker删除。在回应此请求之前,您必须确保收集流上的所有日志,否则可能会丢失日志数据。

此端点上的请求并不意味着该容器仅在已停止的情况下被移除。

请求:

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

响应:

{"Err": ""}

如果在此请求期间发生错误,请将错误消息添加到Err响应中的字段。如果没有错误,那么你可以发送一个空的响应({})或一个空的值的Err字段。

可选端点

日志记录插件可以实现两个额外的日志记录端点:

/LogDriver.Capabilities

定义日志驱动程序的功能。您必须为Docker实现此端点才能利用任何已定义的功能。

请求:

{}

响应

{"ReadLogs": true}

支助能力:

  • ReadLogs - 这告诉Docker该插件能够将日志读回客户端。报告他们支持的插件ReadLogs必须实现/LogDriver.ReadLogs端点/LogDriver.ReadLogs将日志读回客户端。这在docker logs <container>被调用时使用。为了让Docker使用这个端点,插件必须在/LogDriver.Capabilities被调用时指定多少。

请求

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

ReadConfig是阅读选项列表,它定义了一个具有以下golang结构:类型ReadConfig结构{由于尾了time.time int跟随bool}

  • Since定义应该发送的最旧日志。

  • Tail定义要读取的行数(例如,像命令tail -n 10

  • Follow 表示客户希望保持连接状态,以便在读取现有日志后收到新的日志消息。

Info是在中定义的相同类型/LogDriver.StartLogging。它应该用于确定要读取的日志集合。

响应:

响应应该是编码的日志消息,使用与插件从Docker消耗的消息相同的格式。

上一篇: 下一篇: