* docs: remove some leading space
* style: fix whitespace inconsistency
- double spaces in docker commands
- inconsistent indentation in multiline commands and paragraphs
- trailing spaces
The "-settings" suffix in the URL duplicated the "/settings/" directory
in the URL, which made it redundant.
Using "/mac/", "/windows/" and "/linux/" keeps the URLs shorter, more
memorable, and more consistent with other locations, making it easier
to "guess" the URL when navigating using the browser's location bar.
No redirects were added, because the "-settings" pages have not yet
been published.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* network/proxy: add a note pointing at docker engine and Docker Desktop
The title is "Configure Docker to use a proxy server" which is generic
and implies this is the page which describes everything.
However the scope of the instructions is limited to containers:
> If your container needs to use an HTTP, ...
There are other HTTP proxy cases, for example
- for Docker Desktop to log into Docker
- for pulling and pushing containers
- for docker scan
Add a note at the top of this page to clarify the scope and link to
instructions for other cases.
Signed-off-by: David Scott <dave.scott@docker.com>
* Apply suggestions from code review
Co-authored-by: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
* Update proxy.md
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
Co-authored-by: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
Add the `--ipv6` switch to the first example in the "Dual stack IPv4 IPv6 IPvlan L2 mode"
section. WIthout that, the created network has the property EnableIPv6 set to false and the
example wouldn't work properly.
- Add missing code-hints (console, yaml)
- Consistently add an empty line after code-blocks
- Combine some examples where the output and the command were
put in separate blocks. With the "console" code-hint, this
is no longer nescessary.
- fix indentation in cloud/ecs-integration.md, which caused the
numbered-list to be interrupted.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Was setting `ipvlan`, since home router didn't support `macvlan`, and only started working when I noticed elsewhere that I needed to add the `-o parent=eth0` for `ipvlan` setup as it was set for `macvlan`.
The `ENV key value` form can be ambiguous, for example, the following defines
a single env-variable (`ONE`) with value `"TWO= THREE=world"`:
ENV ONE TWO= THREE=world
While we cannot deprecate/remove that syntax (as it would break existing
Dockerfiles), we should reduce exposure of the format in our examples.
Also updating some code-blocks that were missing language-hints
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Fix incorrect links in compose section
there's a bug causing wrapped links to not work, and replacing
some links to point to the .md file, so that IDE's can check
if the anchors are valid. Also replaced some links to point
to their new location.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* engine/swarm: update links
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Fix various broken links
There's a bug in the "jekyll-relative-links" plugin that causes wrapped links to not work.
Also replacing some links to point to the .md file, so that IDE's can check if the anchors
are valid. Finally, replaced some links to point to their new locations, so that users don't
get redirected..
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Remove incorrect difference between user-defined and default bridge
This PR removes the first bullet point from the list differences between user-defined bridge networks and the default bridge network:
[User-defined bridges provide better isolation and interoperability between containerized applications](https://docs.docker.com/network/bridge/#differences-between-user-defined-bridges-and-the-default-bridge).
The default bridge network, similar to user-defined bridges, opens all ports to other containers and allows for inter-container communication by default. This is elaborated and demonstrated in #8973. Other relevant issue: #8437.
* Remove mention of previous bullet point
* Added isolation advantage of user-defined over default network
* Move classic overlay networking topic to swarm standalone section
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Redirect old "getting started with overlay networks" to current page
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* improve description of iptables design, add notes about securing Docker hosts
* fix typo
* simplify a sentence
* fix chain name
* more minor changes
* add notes about the FORWARD chain policy
* shorten section on --ip
* rephrase section title
