* Update trust-with-remote-ucp.md
* Fix link texts
* Addresses 8446
* Update trust_delegation.md
* - Addresses 8446
- Cleans up broken links
- Fixes vague link texts
Addresses 8446
Update trust_delegation.md
* Update running_ssh_service.md
* Update running_ssh_service.md
Fixed formatting and wording. Also moved note above the code.
* Update running_ssh_service.md
Fixed typo.
* Compose: Update build docs, Add --quiet flag
* Fix destroy reference page link
Relates to https://github.com/docker/docker.github.io/pull/8441
* Rephrase Ubuntu 14.04 note
* Revert "Compose: Update build docs, Add --quiet flag"
* # This is a combination of 4 commits.
# This is the 1st commit message:
- Addresses 8446
- Cleans up broken links
- Fixes vague link texts
Addresses 8446
Update trust_delegation.md
# This is the commit message #2:
# This is a combination of 2 commits.
# This is the 1st commit message:
- Addresses 8446
- Cleans up broken links
- Fixes vague link texts
Addresses 8446
Update trust_delegation.md
# This is the commit message #2:
Update trust-with-remote-ucp.md
# This is the commit message #3:
- Addresses 8446
- Cleans up broken links
- Fixes vague link texts
# This is the commit message #4:
Fix destroy reference page link
Relates to https://github.com/docker/docker.github.io/pull/8441
* - Addresses 8446
- Cleans up broken links
- Fixes vague link texts
* Addresses 8446 with text and link cleanup.
* Update syntax language from none to bash
* Update index.md
The current documentation points to use a version of notary which has an expired certicate.
Updated the version of notary_autobuilds to 0.5.1 from 0.4.2.
Change the shared volume to notarycerts:/var/lib/notary/fixtures from notarycerts:/go/src/github.com/docker/notary/fixtures as location of certificate has changed.
As previously stated, the entire `%ProgramData%` directory would be ignored. This also uses a PowerShell syntax for which most people may not be familiar, but most often PowerShell users know how to translate from supported environment variables. The main point is to limit the directory to ignore to just docker. Many, many other applications write to `%ProgramData%`.
Directions around `extfile.cnf` for client certificates was somewhat confusing. Edited the document to clarify that a separate file was to be created, not append a line to the file that had just been created for the server.
* Reword lots of instances of 'will'
* Reword lots of instances of won't
* Reword lots of instances of we'll
* Eradicate you'll
* Eradicate 'be able to' type of phrases
* Eradicate 'unable to' type of phrases
* Eradicate 'has / have to' type of phrases
* Eradicate 'note that' type of phrases
* Eradicate 'in order to' type of phrases
* Redirect to official Chef and Puppet docs
* Eradicate gratuitous 'please'
* Reduce use of e.g.
* Reduce use of i.e.
* Reduce use of N.B.
* Get rid of 'sexagesimal' and correct some errors
As of
66eb2a3e8f
in runc, this is no longer true (in fact, it was never true; the problem
was a bug in runc, not a kernel check). Let's remove it.
Signed-off-by: Tycho Andersen <tycho@docker.com>
This example is leading to confusion when folks populate /etc/sub{g,u}id with dockremap:231072:65536 instead of testuser:231072:65536. Step 4 (verification) of "Enable userns-remap on the daemon" doesn't match if the dockremap uid/gid is used.
* Update fedora.md
add warning class to blogquote
* Update linux-postinstall.md
add warning class to blogquote
* Update ubuntu.md
add warning class to blogquote
* Update https.md
add warning class to blogquote
* Update swarm_manager_locking.md
add warning class to blogquote
* Update dockerlinks.md
add warning class to blogquote
* Update deploying.md
add warning class to blogquote
* Update deploying.md
add warning class to blogquote
* Update insecure.md
add warning class to blogquote
* Update discovery.md
add warning class to blogquote
* Update dockerd.yaml
add warning class to blogquote
* Update docker_secret_rm.yaml
add warning class to blogquote
* Update docker_service_rm.yaml
add warning class to blogquote
* Update docker_secret_rm.yaml
add warning class to blogquote
* Update scale-your-cluster.md
add warning class to blogquote
* Update resource_constraints.md
add warning class to blogquote
* Update binaries.md
add warning class to blogquote
* Update content_trust.md
add warning class to blogquote
* Update secrets.md
add warning class to blogquote
* Update index.md
add warning class to blogquote
* Update install-sandbox-2.md
add warning class to blogquote
* Update docker-toolbox.md
add warning class to blogquote
* Update index.md
add warning class to blogquote
* Update centos.md
add warning class to blogquote
* Update debian.md
add warning class to blogquote
* Update faqs.md
add linebreak after Looking for popular FAQs on Docker for Windows?
* Update install.md
add linebreake after **Already have Docker for Windows?**
* Revert "Update dockerd.yaml"
This reverts commit 3a98eb86f700ade8941483546c33f69a9dab8ac3.
* Revert "Update docker_secret_rm.yaml"
This reverts commit 5dc1e75f37033932486c11287052b7d64bf83e55.
* Revert "Update docker_service_rm.yaml"
This reverts commit a983380a5625b471f1a03f8ed2301ead72f98f1b.
* Revert "Update docker_secret_rm.yaml"
This reverts commit 4c454b883c300e26fbb056b954bb49ec2933b172.
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 trust_key_mng.md
* Update trust_key_mng.md
I don‘t know how the whitespace appears, and it seems that it appears because something happened related to its original format (right-aligned pipe characters) and my change. Still unknown.
Now I've deleted some redundant whitespace.
* Update
I don‘t know how the whitespace appears, and it seems that it appears because something happened related to its original format (right-aligned pipe characters) and my change. Still unknown.
Now I've deleted some redundant whitespace.