- Revised vocabulary to be consistent using 'Docker Content Cache'
- Added 'What is Docker Content Cache' section
- Added examples for deploying with TLS and cache chaining
- Moved configuration table before examples section
Removed "Using default tag: latest" from sample command output. The testing tag was specified in the command, so it would not being using the default tag.
* Update cloud-on-aws-faq.md
* Update cloud-on-aws-faq.md
Revise. Sorry, my thought wandered at that moment<span class="emoji-outer emoji-sizer"><span class="emoji-inner" style="background: url(chrome-extension://immhpnclomdloikkpcefncmfgjbkojmh/emoji-data/sheet_apple_64.png);background-position:67.5% 65%;background-size:4100%" title="dizzy_face"></span></span>
Clarified the sentence on running Linux containers on Windows. You can't do that, but you can run Linux containers with *Docker for Windows*, which spins up a Moby VM for Linux containers.
Compose file v1 and v2 docs had relative links to some non-existing pages (especially about extending services). It was probably introduced when `compose-file.md` was detached into directory with single file per compose file version.
Adjust the upgrade section so it is no longer a subsection of install
Display the bundle link and it only shows UCP images
Signed-off-by: Ryan Zhang <ryan.zhang@docker.com>
* update step_three.md
Update docker hub link by docker store link (docker/whalesay is no more in the results of docker hub search). Would be interesting to update the illustration images with docker store illustrations.
* Update step_three.md
Is my change appropriate? Or shall we list them as two steps as follows:
Before you upgrade your nodes:
1.Go to the detail page, xxx
2.If a new version is available, xxx
Resolves#1732. This separates out the use cases into three audiences:
administrators who configure UCP and HRM, users who use the web UI, and
users who use the Docker CLI or API. The CLI reference also provides a
guide to the label syntax and the full set of features.