From d2c04ba168ac0897133f231b71e61f53ecd2ccd5 Mon Sep 17 00:00:00 2001 From: shiz0 Date: Thu, 5 Mar 2020 20:39:34 +0100 Subject: [PATCH 1/4] Update firststeps-disable_ipv6.md --- docs/firststeps-disable_ipv6.md | 30 ++++++++++++++++++++++-------- 1 file changed, 22 insertions(+), 8 deletions(-) diff --git a/docs/firststeps-disable_ipv6.md b/docs/firststeps-disable_ipv6.md index 3a1f6450c..b6f767d80 100644 --- a/docs/firststeps-disable_ipv6.md +++ b/docs/firststeps-disable_ipv6.md @@ -1,20 +1,34 @@ This is **ONLY** recommended if you do not have an IPv6 enabled network on your host! -If IPv6 MUST be disabled to fit a network, open `docker-compose.yml`, search for `enable_ipv6`... +If you need to, you can disable the usage of IPv6 in the compose file. +Additionally, you can also disable the startup of container "ipv6nat-mailcow", as it's not needed if you won't use IPv6. +Instead of editing docker-compose.yml directly, it is preferrable to create an override file for it +and implement your changes there. + +Go to your mailcow directory and Create a new file called "docker-compose.override.yml": +``` +# cd /opt/mailcow-dockerized +# touch docker-compose.override.yml +``` +**NOTE:** If you already have an override file, of course don't recreate it, but merge the lines below int your existing one accordingly! + +Open the file in your favourite text editor and fill in the following: ``` +version: '2.1' +services: + + ipv6nat-mailcow: + restart: "no" + entrypoint: ["echo", "pv6nat disabled in compose.override.yml"] + networks: mailcow-network: - [...] - enable_ipv6: true - [...] + enable_ipv6: false ``` -...change it to `enable_ipv6: false`. - -mailcow needs to be shutdown, the containers removed and the network recreated: - +For these changes to be effective, you need to fully stop and then restart the stack, so containers and networks are recreated: ``` docker-compose down docker-compose up -d From 8faffdf56d63226e13568c689d2e811b03fe4f46 Mon Sep 17 00:00:00 2001 From: shiz0 Date: Fri, 6 Mar 2020 12:41:13 +0100 Subject: [PATCH 2/4] Update firststeps-disable_ipv6.md --- docs/firststeps-disable_ipv6.md | 27 +++++++++++++++++++-------- 1 file changed, 19 insertions(+), 8 deletions(-) diff --git a/docs/firststeps-disable_ipv6.md b/docs/firststeps-disable_ipv6.md index b6f767d80..fc3948a54 100644 --- a/docs/firststeps-disable_ipv6.md +++ b/docs/firststeps-disable_ipv6.md @@ -1,12 +1,28 @@ This is **ONLY** recommended if you do not have an IPv6 enabled network on your host! -If you need to, you can disable the usage of IPv6 in the compose file. +If you really need to, you can disable the usage of IPv6 in the compose file. Additionally, you can also disable the startup of container "ipv6nat-mailcow", as it's not needed if you won't use IPv6. Instead of editing docker-compose.yml directly, it is preferrable to create an override file for it -and implement your changes there. +and implement your changes to the service there. Unfortunately, this right now only seems to work for services, not for network settings. -Go to your mailcow directory and Create a new file called "docker-compose.override.yml": +To disable IPv6 on the mailcow network, open docker-compose.yml with your favourite text editor and search for the network section (it's near the bottom of the file). +Change ```enable_ipv6: true``` to ```enable_ipv6: false```: +``` +networks: + mailcow-network: + driver: bridge + driver_opts: + com.docker.network.bridge.name: br-mailcow + enable_ipv6: true + ipam: + driver: default + config: + - subnet: ${IPV4_NETWORK:-172.22.1}.0/24 + - subnet: ${IPV6_NETWORK:-fd4d:6169:6c63:6f77::/64} +``` + +To disable the ipv6nat-mailcow container as well, go to your mailcow directory and create a new file called "docker-compose.override.yml": ``` # cd /opt/mailcow-dockerized # touch docker-compose.override.yml @@ -22,12 +38,7 @@ services: ipv6nat-mailcow: restart: "no" entrypoint: ["echo", "pv6nat disabled in compose.override.yml"] - -networks: - mailcow-network: - enable_ipv6: false ``` - For these changes to be effective, you need to fully stop and then restart the stack, so containers and networks are recreated: ``` docker-compose down From d2f19b82f4394692d0eeab0d0b3ebf69c230ecdd Mon Sep 17 00:00:00 2001 From: shiz0 Date: Fri, 6 Mar 2020 12:51:22 +0100 Subject: [PATCH 3/4] Update firststeps-disable_ipv6.md --- docs/firststeps-disable_ipv6.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/firststeps-disable_ipv6.md b/docs/firststeps-disable_ipv6.md index fc3948a54..17505c645 100644 --- a/docs/firststeps-disable_ipv6.md +++ b/docs/firststeps-disable_ipv6.md @@ -23,12 +23,12 @@ networks: ``` To disable the ipv6nat-mailcow container as well, go to your mailcow directory and create a new file called "docker-compose.override.yml": + +**NOTE:** If you already have an override file, of course don't recreate it, but merge the lines below into your existing one accordingly! ``` # cd /opt/mailcow-dockerized # touch docker-compose.override.yml ``` -**NOTE:** If you already have an override file, of course don't recreate it, but merge the lines below int your existing one accordingly! - Open the file in your favourite text editor and fill in the following: ``` @@ -37,7 +37,7 @@ services: ipv6nat-mailcow: restart: "no" - entrypoint: ["echo", "pv6nat disabled in compose.override.yml"] + entrypoint: ["echo", "ipv6nat disabled in compose.override.yml"] ``` For these changes to be effective, you need to fully stop and then restart the stack, so containers and networks are recreated: ``` From 82e46cbe4473e92ab23367dbb771c237b7472e38 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Peters?= Date: Fri, 6 Mar 2020 17:56:25 +0100 Subject: [PATCH 4/4] Update firststeps-disable_ipv6.md --- docs/firststeps-disable_ipv6.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/firststeps-disable_ipv6.md b/docs/firststeps-disable_ipv6.md index 17505c645..9c380dfe9 100644 --- a/docs/firststeps-disable_ipv6.md +++ b/docs/firststeps-disable_ipv6.md @@ -7,7 +7,9 @@ Instead of editing docker-compose.yml directly, it is preferrable to create an o and implement your changes to the service there. Unfortunately, this right now only seems to work for services, not for network settings. To disable IPv6 on the mailcow network, open docker-compose.yml with your favourite text editor and search for the network section (it's near the bottom of the file). -Change ```enable_ipv6: true``` to ```enable_ipv6: false```: + +Change `enable_ipv6: true` to `enable_ipv6: false`: + ``` networks: mailcow-network: @@ -25,10 +27,12 @@ networks: To disable the ipv6nat-mailcow container as well, go to your mailcow directory and create a new file called "docker-compose.override.yml": **NOTE:** If you already have an override file, of course don't recreate it, but merge the lines below into your existing one accordingly! + ``` # cd /opt/mailcow-dockerized # touch docker-compose.override.yml ``` + Open the file in your favourite text editor and fill in the following: ``` @@ -39,7 +43,9 @@ services: restart: "no" entrypoint: ["echo", "ipv6nat disabled in compose.override.yml"] ``` + For these changes to be effective, you need to fully stop and then restart the stack, so containers and networks are recreated: + ``` docker-compose down docker-compose up -d