iv-org/documentation
1
0
Fork 0
mirror of https://github.com/iv-org/documentation.git synced 2024-12-22 22:09:22 -05:00
Code Issues Packages Projects Releases Wiki Activity

remove mention about force_resolve: ipv6

Browse Source
This commit is contained in:
Émilien (perso) 2023-12-01 13:24:07 +00:00 committed by GitHub
parent 570bb7ca4b
commit 8e5cad3280
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/ipv6-rotator.md
View File

@ -55,16 +55,6 @@ Please install:
Other Linux distributions: `sudo yourpackagemanager install python-pyroute2` Other Linux distributions: `sudo yourpackagemanager install python-pyroute2`
## Configure Invidious for IPv6 ## Configure Invidious for IPv6
### If you are running Invidious outside of Docker or using something else than Docker (K8s)
Please make sure that you have this line set in `config.yml`:
```yaml
force_resolve: ipv6
```
Note: If you are on Kubernetes, check that your pods have IPv6 connectivity. But you probably already know that if you are using Kubernetes.
### If you are running Invidious in Docker ### If you are running Invidious in Docker
Note: Make sure you are running a recent version of Docker if you are running into IPv6 issues. Note: Make sure you are running a recent version of Docker if you are running into IPv6 issues.
@ -89,16 +79,12 @@ If needed, IPv6 official documentation for Docker is at https://docs.docker.com/
gateway: 2001:0DB9::1 gateway: 2001:0DB9::1
``` ```
Note: Don't change the subnet and the gateway. Unless there is a conflict with an existing docker network. Note: Don't change the subnet and the gateway. Unless there is a conflict with an existing docker network.
4. Make sure that you have this line set in `config.yml`: 4. Bring down your docker composition and bring it back up for recreating the network:
```yaml
force_resolve: ipv6
```
5. Bring down your docker composition and bring it back up for recreating the network:
``` ```
docker compose down docker compose down
docker compose up -d docker compose up -d
``` ```
6. To check if everything went well then do: 5. To check if everything went well then do:
``` ```
docker compose exec invidious ping -c 1 ipv6.icanhazip.com docker compose exec invidious ping -c 1 ipv6.icanhazip.com
``` ```