* Updated the options docs for journald driver
I have updated the options documentation for the journald logging driver, since I was having trouble understanding how it was supposed to be used. I modeled it heavily after the google cloud logging driver docs, since I found those helpful in solving my own issues.
* Share redoc JavaScript between API versions
The redoc JavaScript is a big file, and there's no need
to keep a separate copy for each version of the API.
This patch removes the copy per-version and moves the script
to a central location.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Use central stylesheet for API reference
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Update ReDoc to v1.19.3
Changelog can be found at https://github.com/Rebilly/ReDoc/blob/v1.19.3/CHANGELOG.md
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Hide "request type" badges in menu
ReDoc 1.13 added "request type" badges in the menu
given that we didn't show these before, this patch
hides them.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Add .map file for ReDoc
Having a .map file allows debugging script issues
in the ReDoc JavaScript (which is minified).
It's a big file, but may be useful to have.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This feature was introduced in Docker 17.07, so has
been available in stable release 17.09 and up.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
If your wanting to installed a specific version of Docker EE on Windows 2016 the -RequiredVersion flag works better than the `MaximumVersion`,`MinimumVersion`.
* Make 'use a process manager' clearer
The "Use a process manager" section appears to mix use of process manager on host with using process managers within a container.
The essence of the section appears to suggest that host-level process managers are ok as long as you don't combine them with docker restart policies. But paragraphs 2 & 3 (in the original) seem to actively discourage the use of process managers within containers. Putting paragraphs 2 & 3 under an explicit heading would be clearer.
Should a section on process mangers within containers be expanded? There are lots of articles on the internet that relate to using process managers to start multiple processor in containers or to manage zombie pid 1 processes. Are there official recommendations on what to do in these situations — whether to use a process manager or is a recommended 'docker native' way to achieve the same results?
* Updated to use the warning class
Spend "a few hours" on MACVLAN set up to get host machine access containers and finally found out that the setting on /etc/network/interface is not correct in this doc. After adding dash to "pre-up" and "pre-down" and restarting the interface (sudo ifdown mac0 && sudo ifup mac0) everything started working like a charm.
Misty Stanley-Jones