From f32e5d083fd57fcf96a154e80064a84dae7e7b99 Mon Sep 17 00:00:00 2001 From: deon Date: Mon, 27 May 2024 04:19:58 +0000 Subject: [PATCH] Update IPv6 example --- Installation.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Installation.md b/Installation.md index 4bdeb98..9387cd3 100644 --- a/Installation.md +++ b/Installation.md @@ -127,7 +127,7 @@ services: networks: default: public: - ipv6_address: ${IP6_PREFIX}:${IP6_SUFFIX}::2 + ipv6_address: ${IP6_PREFIX}:${IP6_SUFFIX}:2 aliases: - clrghouz hostname: ${WEB_HOSTNAME} @@ -182,7 +182,7 @@ services: networks: default: public: - ipv6_address: ${IP6_PREFIX}:${IP6_SUFFIX}::3 + ipv6_address: ${IP6_PREFIX}:${IP6_SUFFIX}:3 sysctls: - "net.ipv6.conf.all.disable_ipv6=0" volumes: @@ -267,7 +267,7 @@ services: networks: default: public: - ipv6_address: ${IP6_PREFIX}:${IP6_SUFFIX}::f + ipv6_address: ${IP6_PREFIX}:${IP6_SUFFIX}:f ports: - "24553:24553" - "24554:24554" @@ -288,7 +288,7 @@ networks: ipam: driver: default config: - - subnet: ${IP6_PREFIX}:${IP6_SUFFIX}::/96 + - subnet: ${IP6_PREFIX}:${IP6_SUFFIX}::/112 gateway: ${IP6_PREFIX}:${IP6_SUFFIX}::1 ``` @@ -298,7 +298,7 @@ Also make an `.env` file, that is placed in your clrghouz directory (`/srv/docke # Clrghouz Details #IMAGE=gitea.dege.au/bbs/clrghouz IP6_PREFIX=[IP6_PREFIX] -IP6_SUFFIX=0d0c:0100 +IP6_SUFFIX=0d0c:0100:f1d0 #VOL_PREFIX=/srv/dockerclrghouz APP_KEY=[APP_KEY] @@ -337,7 +337,7 @@ _NOTES:_ * This docker compose file should be called `docker-compose.yml` for it to be found automatically. * You'll defined the `[APP_KEY]` below * Update the `[IPv6_PREFIX]` as appropriate for your setup. This assumes you have your IPv6 setup, and you have configured your router to route this prefix to this host running clrghouz. - The example I use here `[IPv6_PREFIX]:0d0c:100::/96` is because my docker hosts run many applications, and I want each application to have its own segment. So I route `[IPv6_PREFIX]:0d0c:100::/88` to the docker host, which ultimately provides me with 256 `/96` networks, with each network having more than enough addresses I can use. + The example I use here `[IPv6_PREFIX]:0d0c:100:f1d0::/112` is because my docker hosts run many applications, and I want each application to have its own segment. So I route `[IPv6_PREFIX]:0d0c:0100::/88` to the docker host, which ultimately provides me with lots of `/112` networks, with each network having more than enough addresses I can use. * Create a suitable `[DB_PASSWORD]` and update your docker-compose file. * We'll define `[MINIO_ACCESS_KEY]` and `[MINIO_SECRET_KEY]` later - and you'll update your docker-compose file with those details. * If you dont want to use haproxy, then you can comment/delete out this section in the docker-compose file. You'll also need to uncomment the post definitions in the _web:_ section.