simplified the workflow title
WIP: graphical and format updates for workflow steps on home page
working on better formatting for subtopic bullets
formatting updates and wording tweaks to workflow on home page
wording tweak on app tutorial where to learn more
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
added links to the glossary for image and container
updated diagram colors, added sketch source file
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
added instructions on how to directly download .yml file from GitHub
added more detail on how to get to a raw file in GitHub
further clarified how to get to and download the .yml file on GitHub
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
debian does not have linux-image-extra-virtual or linux-image-extra-$(uname -r) packages. the author might have used a debian based distribution. debian kernels come with the aufs modules per default, no need to install extra packages.
added more concept definitions to intro topics
copy edit to clarify something
changed topic title
updated topic title in TOC as well
text formatting, re-push for new Jenkins
fixed installer download buttons in Getting Startd to specify a button type
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
`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".
this source file no longer exists on "master",
so replacing the link with a permalink on the
1.13 tag.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
The apt repo layout seems wrong, it only worked after the proposed change.
Also apt-key seems to need `-` to look at stdin; otherwise I got `gpg: can't open `': No such file or directory`
* take a stab at fixing a broken link
Signed-off-by: LRubin <lrubin@docker.com>
* Update systemd.md
Removed the quotes from the --graph option on line 130. Using quotes works for version 1.12 of Docker but with 1.13, Docker will create a directory named <double-quotes> under / and then create a directory of mnt/docker-data" under that directory.
The documentation describes that the "testing" repository
is disabled by default;
> Optional: Enable the testing repository. This repository
> is included in the docker.repo file above but is disabled
> by default.
However, the repo-files had the testing repo enabled.
This patch updates the repo-files to disable the
repository by default.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Fix title in Engine API getting started
A weird character was causing it to not be rendered correctly.
Signed-off-by: Ben Firshman <ben@firshman.co.uk>
* Update getting-started.md
With the past version the apt-get update results in a 403 for the docker repository when using a Jessie. Looking at the repo structure I assume that now will also work on the other Debian releases.
The repo-files used in the installation instructions currently use `$releasever`
to configure the right YUM repository to use, however _Server_ releases output
the version in a different format (i.e., `7Server` instead of just `7`).
Given that we don't have separate repositories for "Server" and "Desktop" editions,
and we only support version 7, setting the repo-files to use a fixed version.
This issue was originally reported in
https://github.com/docker/docker/issues/23376
And fixed through 2b36087597, but this change
got lost during the rewrite of the installation docs.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
The yum-utils package is not installed by default
on some cloud providers, causing the
`yum-config-manager --add-repo` step to fail.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Victoria Bialas