* Logging driver port from vnext-engine
* Update json-file.md
* Update json-file.md
* Port changes from vnext-engine
* Updates based on feedback
* Added note back in
* Added note back in
* Added limitations per Anusha
* New dual logging info
* Added link to new topic
Needs verification.
* Changes per feedback.
* Updates per feedback
* Updates per feedback
* Updated 20m
* Added CE version
* Added missing comma
* Updates per feedback
* Add raw tag
Add TOC entry - subject to change
* Add entry for local logging driver
* Update config/containers/logging/configure.md
Co-Authored-By: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
* Update config/containers/logging/configure.md
Co-Authored-By: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
* Update config/containers/logging/configure.md
Co-Authored-By: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
* Update config/containers/logging/configure.md
Co-Authored-By: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
* Updates per feedback
* Updates per feedback
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>
This approach works on all platforms, and reduces the dependency
on external tools (`grep` in this case).
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Docker Engine 17.05 has reached EOL, so all current versions of the
Docker Engine now support this feature.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Replace all occurrences of
```foo
{% raw %}
bar
{% endraw %}
```
(which generates spurious empty lines in the rendered pre block) with
{% raw %}
```foo
bar
```
{% endraw %}
Also, fix some occurrences where the raw section is too large and
prevented interpretation of Jekyll directives.
This is the syntax used in the documentation of Jekyll itself:
https://raw.githubusercontent.com/jekyll/jekyll/master/docs/_docs/templates.md
FTR, done with two perl substitutions:
'^([\t ]*```[^\n]*
)([ \t]*\{% raw %\}[^\n]*
)' '$2$1'
and
'^([ \t]*\{% endraw %\}[^\n]*
)([\t ]*```[^\n]*
)' '$2$1'
and manually tweaks. A mechanical check would be most useful.
Signed-off-by: Akim Demaille <akim.demaille@docker.com>
- 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
Usha Mandya
Sobhan Attar
Sebastiaan van Stijn
Fangzhou Li
Bertrand Guay-Paquet
Maria Bermudez
Russell Ballestrini
Anne Henmi
Anne Henmi
Akim Demaille
Misty Stanley-Jones