From c63f7039fa2ebcae633eb56a7b2ed8be819b0367 Mon Sep 17 00:00:00 2001 From: David Scott Date: Thu, 3 Jun 2021 14:32:49 +0100 Subject: [PATCH] Desktop: after changing IP both Kube and Swarm need to be re-initialised Signed-off-by: David Scott --- docker-for-mac/networking.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docker-for-mac/networking.md b/docker-for-mac/networking.md index c8bbbf0829..a1f055d081 100644 --- a/docker-for-mac/networking.md +++ b/docker-for-mac/networking.md @@ -48,6 +48,12 @@ See [Proxies](index.md#proxies). Following is a summary of current limitations on the Docker Desktop for {{Arch}} networking stack, along with some ideas for workarounds. +### Changing internal IP addresses + +The internal IP addresses used by Docker can be changed via the Settings (Windows) +or Preferences (Mac). After changing IPs, it is necessary to reset the Kubernetes +cluster and to leave any active Swarm. + ### There is no docker0 bridge on macOS Because of the way networking is implemented in Docker Desktop for Mac, you cannot see a