Maksytka/kind
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/kind.git synced 2025-12-01 07:26:05 +07:00
Code Issues Packages Projects Releases Wiki Activity

Add known issue "Docker Desktop for macOS and Windows"

Browse Source
This commit is contained in:
Domenico Andreoli
2022-05-31 14:10:19 +02:00
parent d2d69ffb9f
commit 26855d4fb5
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
site/content/docs/user/known-issues.md
View File

@@ -42,6 +42,7 @@ description: |-
* [Fedora](#fedora) (various)
* [Failed to get rootfs info](#failed-to-get-rootfs-info--stat-failed-on-dev)
* [Failure to Create Cluster with Docker Desktop as Container Runtime](#failure-to-create-cluster-with-docker-desktop-as-container-runtime)
* [Docker Desktop for macOS and Windows](#docker-desktop-for-macos-and-windows)
## Troubleshooting Kind
@@ -415,3 +416,9 @@ restarting the Docker Engine, the VM used by Docker Desktop will use cgroupv1.
[AppArmor]: https://en.wikipedia.org/wiki/AppArmor
[firewalld]: https://firewalld.org/
[inotify]: https://en.wikipedia.org/wiki/Inotify
## Docker Desktop for macOS and Windows
Docker containers cannot be executed natively on macOS and Windows, therefore Docker Desktop runs them in a Linux VM. As consequence, the container networks are not exposed to the host and you cannot reach the kind nodes via IP. You can work around this limitation by configuring [extra port mappings](https://kind.sigs.k8s.io/docs/user/configuration/#extra-port-mappings) though.
Just for macOS, you may consider [Docker Mac Net Connect](https://github.com/chipmk/docker-mac-net-connect) (MIT license). It manages an IP tunnel between the host and the Linux VM, adjusting the routing according to the Docker networks and seamlessly restoring the connectivity to Docker containers and kind nodes.