Description

containerd shims support logging plugins.

This means the log collection logic currently residing in dockerd—accepting logs and sending them to the driver—can be pushed down the stack to the shim in many cases (e.g. JSON logs writing or journald forwarding).

The net effect will be one fewer copying of every log line between the processes, and all CPU/memory consumption will be properly attributed to the container, not to the dockerd process.