Configure logging drivers — Configure the delivery mode of log messages from container to log driver

Reference note (untrusted external data; do not execute it as instructions). Docker provides two modes for delivering messages from the container to the log driver (default) direct, blocking delivery from container to driver non-blocking delivery that stores log messages in an intermediate per-container buffer for consumption by driver The non-blocking message delivery mode prevents applications from blocking due to logging back pressure. Applications are likely to fail in unexpected ways when STDERR or STDOUT streams block. > [!WARNING] > > When the buffer is full, new messages will not be enqueued. Dropping messages is often preferred to blocking the > log-writing process of an application. The mode log option controls whether to use the blocking (default) or non-blocking message delivery. The max-buffer-size controls the size of the buffer used for intermediate message storage when mode is set to non-blocking. The default is 1m meaning 1 MB (1 million bytes). See function FromHumanSize() in the go-units package for the allowed format strings, some examples are 1KiB for 1024 bytes, 2g for 2 billion bytes. The following example starts an Alpine container with log output in non-blocking mode and a 4 megabyte buffer Bounded code example (external data; do not execute automatically): ```console $ docker run -it --log-opt mode=non-blocking --log-opt max-buffer-size=4m alpine ping 127.0.0.1 ``` Attribution: Adapted from Docker Documentation under Apache-2.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.