Skip to content

Commit

Permalink
Document how IPv6-only works in Docker Desktop
Browse files Browse the repository at this point in the history 
Signed-off-by: Albin Kerouanton <[email protected]>
  • Loading branch information
@akerouanton
akerouanton committed Sep 17, 2024
1 parent 23f3fbd commit 69a6e75
Showing 1 changed file with 27 additions and 0 deletions.
27 changes: 27 additions & 0 deletions content/manuals/desktop/networking.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -184,3 +184,30 @@ to give the container direct access to the network stack of the host.

See the [run command](/reference/cli/docker/container/run.md) for more details on
publish options used with `docker run`.

### IPv4-only, Dual-stack and IPv6-only

{{% experimental title="Beta" %}}
This feature is currently in [Beta](../release-lifecycle.md#beta).

The exact semantics of all three options might change in future releases.
{{% /experimental %}}

Starting with v4.35, Docker Desktop has new options to configure how the VM behaves and the default
settings applied to Docker networks. Dual-stack is the default mode.

In IPv4-only mode, the DNS resolver embedded in the VM only serves A (= IPv4) records and
suppresses any AAAA (= IPv6) records. This might be useful if some of your containerized software

Check warning on line 200 in content/manuals/desktop/networking.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.Acronyms] ' AAAA' has no definition.

Raw Output:
{"message": "[Docker.Acronyms] ' AAAA' has no definition.", "location": {"path": "content/manuals/desktop/networking.md", "range": {"start": {"line": 200, "column": 15}}}, "severity": "WARNING"}
try to connect to IPv6 addresses but your host doesn't have proper IPv6 connectivity.

In Dual-stack mode, both A and AAAA records are served by the DNS resolver. Docker networks are

Check warning on line 203 in content/manuals/desktop/networking.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.Acronyms] ' AAAA' has no definition.

Raw Output:
{"message": "[Docker.Acronyms] ' AAAA' has no definition.", "location": {"path": "content/manuals/desktop/networking.md", "range": {"start": {"line": 203, "column": 31}}}, "severity": "WARNING"}
created with an IPv4 subnet assigned, but no IPv6 subnet. You must pass the `--ipv6` flag to
[`docker network create`](https://docs.docker.com/reference/cli/docker/network/create/#options),
or put [`enable_ipv6: true`](https://docs.docker.com/reference/compose-file/networks/#enable_ipv6)
in network declarations in Compose files.

In IPv6-only mode, the DNS resolver serves only AAAA records, and Docker Engine assigns IPv6

Check warning on line 209 in content/manuals/desktop/networking.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.Acronyms] ' AAAA' has no definition.

Raw Output:
{"message": "[Docker.Acronyms] ' AAAA' has no definition.", "location": {"path": "content/manuals/desktop/networking.md", "range": {"start": {"line": 209, "column": 48}}}, "severity": "WARNING"}
subnets (but no IPv4) by default to your networks. This might be useful if you run Docker Desktop
in an environment where IPv4 is getting phased out but has not been entirely shut down yet.

For more details about IPv6 in Docker Engine refer to [Use IPv6 networking](/manuals/engine/daemon/ipv6.md)

0 comments on commit 69a6e75

Please sign in to comment.