- 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>
* Add --service-ports note to ports section
## Description
Add note in `ports` section of file reference docs pointing to the `run` command's `--service-ports` flag
## Motivation
Spent quite a few hours spinning my wheels before I came across `run`'s `--service-ports` flag.
I'm struggling to find the issue where I found this, but the comment pointing to `--service-ports` had a lot of reacts, so this might be a relatively common
## Things I'd still like to do
- [ ] link to the [`--service-ports` docs](https://github.com/docker/docker.github.io/blob/master/compose/reference/run.md) -- not sure how to do this
- [ ] clean up location of this note -- not sure if I've put the note in a good place -- we can shunt it to the bottom
- [ ] Duplicate for older versions
Thanks
* Minor style update
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
* Change wording to match "docker rm -f" command
Wording says *stop* when the corresponding command is `docker rm -f`.
* Clarify stop and remove
As the container is still running, this step stops the container and then removes it.
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
While dual-logging is enabled automatically, it is possible to disable
this feature, or to configure the default options. This patch adds
documentation for these options.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Looks like all links on the Mirantis docs website are broken and now showing
a 404, so those redirects are no longer useful.
This changes the redirects to go to our homepage instead; we can make
additional tweaks and/or create more specific redirects in a follow-up.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Change the repository link to open an issue on docker scan plugin
Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
* Remove the statement on trials
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
We don't want users to copy the prompt and process output in
"console" blocks, but for other code blocks (bash scripts, yaml)
copying comments should not be disabled.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
The code-blocks did not include line-continuation (`\`) symbols, causing
the code-highlighter to treat them as "process output", which is excluded
from copying/selecting.
Also made some minor touch-ups in markdown while working on this page.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Adding in points to clarify usage of official images
* Minor style update
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
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>