- move "docker desktop" to the top of the "product manuals" section,
and make it the default page
- Add a "Reference documentation" menu item to the TOC, which will be
the "active" menu item when opening the reference section.
- move the "Samples home" menu item outside of the "samples" sub-menu,
and add it at the top level as "samples overview", so that the "index"
highlights that menu-item without opening the "samples" sub-menu. The
"samples" submenu contains various samples which are a bit outdated,
so probably shouldn't be _that_ prominent when opening the page.
Moving the menu item also makes the "breadcrumb" navigation more
natural (moving from a sample to "samples overview" navigates back
to the "top" of the samples section.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
The docker for mac "toolbox" migration page was not accessible as it
was redirected, so removing that page and related images.
This page contained instructions to backup images, which was described
elsewhere, so removing that part in favor of a link to the (better maintained)
content in the "desktop" section.
Also move the migration page that was located inside the "for windows"
directory to a "toolbox" directory, which matches the location inside the
TOC.
Finally; remove the "troubleshooting" entry from the TOC, as it was
redirecting to the migration page (and was under the "kitematic" section,
which was confusing).
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Both Docker Desktop for Mac and Docker Desktop for Windows provide
this feature, so moving it out of the section that's specific to
Docker Desktop for Mac.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
- The /samples/wordpress/ location collided with an old redirect
to the official images, so removed the redirect
- Removed the sshd example from the table and TOC, as the example
was removed, and now pointing to an alternative examples. The
page is kept for people that may have bookmarked it, but no
need to include it in the navigation.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Unifying all "examples" in this directory; some of these should still be
reviewed and/or removed in favor of examples from "awesome compose"
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
these commands are hidden in the cli, but functional, and mentioned
in the "working with buildx" introduction.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Combine Windows install pages
Signed-off-by: Usha Mandya <usha.mandya@docker.com>
* Apply suggestions from code review
Co-authored-by: Stefan Scherer <stefan.scherer@docker.com>
* Apply suggestions from code review
Co-authored-by: Stefan Scherer <stefan.scherer@docker.com>
* Some more minor updates to improve readability
Signed-off-by: Usha Mandya <usha.mandya@docker.com>
Co-authored-by: Stefan Scherer <stefan.scherer@docker.com>
This started as a "fix some links", but reading the section, I found various
issues that could use some improvement. After that, I noticed that both the
Windows and Mac pages had the same content, so I moved this to a common page
instead.
Note that there's still additional information that should likely be included
(and perhaps a rewrite into "per topic" headings (containers, images, ...).
Things that are missing;
- backup/restore swarmkit configs
- backup/restore swarmkit secrets
- backup/restore CLI configuration, trust data etc.
What I did in this pull request:
- recommend pushing images to Docker Hub as the default approach to back up
images (but kept `docker image save` as an alternative)
- recommend `docker container commit` to save containers to an image, as doing
so preserves both the container's configuration _and_ filesystem changes.
`docker container export` only preserves the filesystem, but all other
configuration is lost, which makes it hard to restore a container from it.
Using `docker container commit` (committing the container to an image) also
allows to follow the same procedure to backup containers as for images
(both allowing them to be pushed to a registry, or to a file).
- added some information about "wether or not" containers should be backed
up, as it may not be needed to back up containers if all data is stored
in volumes (best practice).
- added some warnings regarding "sensitive data" (environment variables),
and links to making repositories private before pushing.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Sebastiaan van Stijn
Usha Mandya
Oliver Frolovs
Usha Mandya
Nicolas De Loof
Metal
Sebastiaan van Stijn
Anca Iordache