History

Brian Goff 02677bc06e Add docker plugin upgrade This allows a plugin to be upgraded without requiring to uninstall/reinstall a plugin. Since plugin resources (e.g. volumes) are tied to a plugin ID, this is important to ensure resources aren't lost. The plugin must be disabled while upgrading (errors out if enabled). This does not add any convenience flags for automatically disabling/re-enabling the plugin during before/after upgrade. Since an upgrade may change requested permissions, the user is required to accept permissions just like `docker plugin install`. Signed-off-by: Brian Goff <cpuguy83@gmail.com>		2017-06-02 00:10:52 +00:00
..
extend	Add `capability` filter to `docker plugin ls`	2017-06-02 00:10:51 +00:00
reference	Add docker plugin upgrade	2017-06-02 00:10:52 +00:00
README.md	Sync docker/docker refs with files mistakenly edited in docker.github.io repo	2017-06-02 00:10:26 +00:00
deprecated.md	deprecate "top-level" network information in NetworkSettings	2017-06-02 00:10:44 +00:00

The non-reference docs have been moved!

The documentation for Docker Engine has been merged into the general documentation repo.

See the README for instructions on contributing to and building the documentation.

If you'd like to edit the current published version of the Engine docs, do it in the master branch here: https://github.com/docker/docker.github.io/tree/master/engine

If you need to document the functionality of an upcoming Engine release, use the vnext-engine branch: https://github.com/docker/docker.github.io/tree/vnext-engine/engine

The reference docs have been left in docker/docker (this repo), which remains the place to edit them.

The docs in the general repo are open-source and we appreciate your feedback and pull requests!