From 897f05ee0f5b3126ef140bf5c3f01df3e1ec0bbb Mon Sep 17 00:00:00 2001 From: Simon L Date: Wed, 3 May 2023 18:12:32 +0200 Subject: [PATCH] add suggestion Signed-off-by: Simon L Co-authored-by: Zoey Signed-off-by: Simon L. --- docker-ipv6-support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker-ipv6-support.md b/docker-ipv6-support.md index 09878219..eefbba37 100644 --- a/docker-ipv6-support.md +++ b/docker-ipv6-support.md @@ -36,7 +36,7 @@ On Windows and macOS which use Docker Desktop, you need to go into the settings, ``` 2. Add these values to the json and make sure to keep the other currently values and that you don't see `Unexpected token in JSON at position ...` before attempting to restart by clicking on `Apply & restart`. -3. Make sure that ipv6 is enabled for the internal `nextcloud-aio` network by running `docker network inspect nextcloud-aio`. On a new instance, this command should return that it did not find a network with this name. Then you can run `docker network create --subnet="172.30.1.0/24" --subnet="2001:db8:2::/64" --driver bridge --ipv6 nextcloud-aio` in order to create the network with ipv6-support. If it finds the network though and its value `EnableIPv6` is set to false, make sure to follow https://github.com/nextcloud/all-in-one/discussions/2045 in order to recreate the network and enable ipv6 for it. +3. Make sure that ipv6 is enabled for the internal `nextcloud-aio` network by running `docker network inspect nextcloud-aio`. On a new instance, this command should return that it did not find a network with this name. Then you can run `docker network create --subnet="2001:db8:2::/64" --driver bridge --ipv6 nextcloud-aio` in order to create the network with ipv6-support. If it finds the network though and its value `EnableIPv6` is set to false, make sure to follow https://github.com/nextcloud/all-in-one/discussions/2045 in order to recreate the network and enable ipv6 for it. ---