It was discovered that compression in gelf logging driver
is highly inefficient in terms of CPU. IOW, lots of CPU
is used when compression is enabled.
The natural solution would be to change the default
to `none`, i.e. no compression, but that would break
some setups (in particular, using Logstash < 7.4).
The only option left is to warn the user about the
consequences of leaving the compression enabled.
For more background details, please see
https://github.com/moby/moby/pull/40101
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
log-opts are passed to logging-drivers as-is, so the daemon is not
aware what value-type each option takes.
For this reason, all options must be provided as a string, even if
they are used as numeric values by the logging driver.
For example, to pass the "max-file" option to the default (json-file)
logging driver, this value has to be passed as a string;
```json
{
"log-driver": "json-file",
"log-opts": {
"max-size": "10m",
"max-file": "3"
}
}
```
When passed as a _number_ (`"max-file": 3`), the daemon will invalidate
the configuration file, and fail to start;
unable to configure the Docker daemon with file /etc/docker/daemon.json: json: cannot unmarshal number into Go value of type string
This patch adds an example to the daemon.json to show these values
have to be passed as strings.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
- Move /engine/admin/ and /engine/userguide/ topics to /config/ and /develop/
- Get rid of some stub topics that are no longer needed
- Rename /engine/article-img/ to /engine/images/
- Mark ambassador linking topic as obsolete
- Flesh out multistage build topic
- Reorganize some terribly obsolete content in other files
Sebastiaan van Stijn