You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site/content/docs/user/known-issues.md
+15-14Lines changed: 15 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -419,22 +419,23 @@ have been necessary to resolve this issue.
419
419
420
420
## VPN CIDR Clashes
421
421
422
-
KIND creates a separate docker network named `kind` that will be configured with default IPAM settings. If your host's VPN configuration overlaps with this default range (172.17.x.x) you
423
-
will be unable to access your KIND clusters from outside of the container. The network that is created persists even after the last KIND cluster is deleted, so you can resolve this
424
-
by configuring the network manually before use. For example:
425
-
426
-
```sh
427
-
# stop your KIND cluster
428
-
kind delete cluster
429
-
430
-
# delete the docker network
431
-
docker network rm kind
432
-
433
-
# create a new network with a non-conflicting CIDR
434
-
docker network create --subnet=10.253.0.0/22 kind
422
+
KIND creates a separate docker network named `kind` that will be configured with default IPAM settings. If you are using the default IPAM configuration in your `daemon.json` you
423
+
may have conflicts with existing VPNs that route the 172.17.x.x networks. To resolve this you can reconfigure the daemon-wide IPAM so that all networks will be created in subnets
424
+
that do not have these conflicts.
425
+
426
+
An example configuration that you can add to your `daemon.json` is below. This would configure `10.253.0.0/16` as the defauld CIDR with each individual network receiving a /24
427
+
subnet to use for allocation.
428
+
429
+
```json
430
+
"default-address-pools": [
431
+
{
432
+
"base": "10.253.0.0/16",
433
+
"size": 24
434
+
}
435
+
]
435
436
```
436
437
437
-
NOTE: You will need to configure/create the network again should you execute a `docker prune` or other operation that may lead to the network being deleted.
438
+
For more information on the Docker Engine config file check out [these docs](https://docs.docker.com/engine/daemon/).
0 commit comments