- remove mention of "experimental" for buildx
- use "console" where possible
- removed use of Bash "heredoc" in example, which may not work on
shells other than Bash
- wrap content to ~80 chars
- enable TOC on page
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Docker Desktop 2.x is deprecated, so any current version of Desktop
ships with buildx and the requirements to use multi-arch.
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>
BuildKit allows using alternative Dockerfile syntaxes to introduce new features
without having to update Docker itself. The general recommendation is to always
specify a "syntax" directive in a Dockerfile, so that (if needed) older versions
of Docker can download the correct syntax to build the Dockerfile.
This updates our examples to include a syntax directive, to make users more familiar
with these directives, and to illustrate best-pracitces in our documentation.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
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>
* Add docs for Vuln scanning and troubleshoot updates
Signed-off-by: Usha Mandya <usha.mandya@docker.com>
* Add new section on Desktop support
Signed-off-by: Usha Mandya <usha.mandya@docker.com>
* Fix review comments and add support section for Windows
* Replace existing screenshots with optimized versions
This topic was removed in 9bebb666d9
We may want to add back the part describing sharing sshagent somewhere,
which is not really a feature related to osxfs. Also, some generic
description about file sharing (permissions, syncing) should probably
be added back.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* - Added a new Overview topic for Docker Desktop
- Moved Dashboard up one level and removed OS-specific topics and images from the Mac and Windows directories
* Updated the Desktop TOC
- Moved Install topics above Getting started topic
- Moved Open source licensing up one level
- Removed OS-specific topics
* Fix review comments
