If set to `"mtu": "1500"` will got an error:
```
unable to configure the Docker daemon with file /etc/docker/daemon.json: json: cannot unmarshal string into Go value of type int
```
That code can not unmarshal string into Go value of type int, I changed the type from string to int.
1. remove step 8 from "Configure direct-lvm mode for production" session.
2. change "0 = disabled" to "100 = disabled" in step 10 for thin_pool_autoextend_threshold.
* 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.
* Create index.md
* Create part2.md
* Create part3.md
* Create part4.md
* Create part5.md
* Rewrite step 2
* Update part2.md
* Update part2.md
* Update part2.md
* Update part2.md
* Update part2.md
* Update part2.md
* Update index.md
* Rewrite of part 3
* Tabs-based swarm instructions, pass 1
* Rewrite of parts 3 and 4, tabs implementation
* Navigation, rewrites, part 4 completion
* Part 5 w/Redis
* Part 5, compelte Redis, rename part 6
* TOC/redirect implementation
* Update part6.md
* Changing links to point to new tutorial
* Rewrites and asciinemas
* Fix overview
* Label diagrams
* Fix button
* Fix link to where Stacks are covered
* Fix typo
* s/file/directory
* Reformat paragraph
* Shorten tabs
* Typos
* Release DTR 2.2.4, 2.1.6
* Go back to small /edge (#2736)
* Go back to small /edge
* Update site front page
Add info about Editions
Reorganize components
Update headings
* Move logic of fetching content to a script
* Add v1.28 API
* Add info about versioned API
* Fix a few 404s (#2785)
* Fix typo
* Propose use of another word (#2791)
I think that interested is better than invested, in this case.
* Update secrets.md (#2780)
remove correct secret
* Change mount syntax on windows from //c/ to c:\ (#2761)
LGTM
* Update hackathon.md (#2773)
* nodes.md grammar correction (#2802)
* Grammar and formatting check (#2797)
* Wrong article
If the first word starts with a vowel sound you use an. If the first word has a consonant sound use a.
* Making the text bold
Removing backticks because probably the text needs to be bold and not marked as code.
* Update overview.md (#2805)
It should say 'predecessors', not 'successors'. Otherwise the sentence and the subsequent example don't make sense.
* shrink some big images (#2798)
Signed-off-by: Cristian Staretu <cristian.staretu@gmail.com>
* #2627 (#2804)
- Fix right sidebar overflow on rescale
* Update hackathon.md
* change pre-build to pre_build to remove confusion (#2813)
* change pre-build to pre_build to remove confusion
* clarify that pre_build hook refers to a file
* Update TOC to sentence case (#2790)
* add more info about DTR on the overview page (#2794)
fix#1904
* Update glossary.yaml (#2807)
Fix#2575.
* fix imports since docker api pkg migration, fix example repository name to be canonical (#2806)
* tweak: code format for filename (#2829)
* tweak: code format for filename
slight reword, so as to avoid confusion w/filename
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* small changes just to kick build again
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* Update hackathon.md
* fix broken links (#2808)
* fix broken link (#2809)
* [CONTRIBUTING] update broken link (#2826)
* [Debian] add gnupg2 requirement for stretch (#2823)
* TOC/redirect implementation
* Changing links to point to new tutorial
* Rewrites and asciinemas
* Fix bad merge
* Metadata, formatting
* Front page formatting, link instrumentation
At the current time, Docker flushes any pre-existing DOCKER and DOCKER-ISOLATION chains, meaning that the previous advice was misleading and led users in the wrong direction regarding restricting access to containers via iptables.
* Step 2 is incomplete
Step 2 asks you to install the LVM2 package however instructions on how to do this are missing. I've added that in for completeness.
Example commands for creating a base image do not work due to multiple issues.
- 16:04 not a valid tag for ubuntu image
- apt-get install fails without preceeding `apt-get update`
- gcc command fails without `-nostartfiles` flag
- `docker run` without the `--rm` leaves behind containers which is unintuitive, and inconsistent with the build image used above.
`overlay2` was incorrectly included as a filesystem that the `overlay` and `overlay2` storage drivers can't run on. `overlay2` is the name of the storage driver, but the filesystem is just called `overlay`. It was called `overlayfs` in older versions or the kernel, which would have helped disambiguate this, but I think we should continue to use `overlay` as the name of the filesystem because that's what the kernel uses now.
Previous language indicated that a user would be "creating a thin pool". This language is confusing as it indicates that the logical volume created is of the thin pool type; instead, the volume being created is a linear volume group which is then converted to a thin pool in step 6. This is an important nuance when implementing setup through configuration management tools such as Salt or Ansible. When initially provisioning the two logical volumes as thin pool, the error "Pool metadata LV docker/thinpoolmeta is of an unsupported type".
Misty Stanley-Jones