I’m facing an issue on my macOS system when using Docker (without any containers running) and an AWS VPN simultaneously. Whenever Docker is active, the VPN crashes. I suspect it could be related to DNS, subnet settings, or the bridge network configuration.
Here’s what I’ve tried so far:
Edited the Docker daemon to change the subnet, but it didn’t resolve the issue.
Has anyone encountered a similar problem? Are there specific configurations or workarounds that might help Docker and the AWS VPN coexist without conflict? Any guidance or suggestions would be greatly appreciated.
Docker Desktop has its own subnet but that cannot affect the host system. It is like having a LAN network that cannot break the internet. It is an internal network and doesn’t exist outside of the VM.
I could more esily imagine that Docker Desktop crashes than a crashing VPN, so I don’t really have a good idea here, but I don’t think a subnet inside a VM could not cause it.
Maybe there are some packages that Docker Desktop sends automatically that the VPN could not handle? You can try to disable some features to test this idea. For example “Send usage statistics” in the general settings, but you can disable anything that you don’t use. Then stop Docker Desktop and start again, don’t just restart it, because some features may stay activated until completely stopping Docker Desktop.
You can also change the virtual machine manager and see if any of those fixes anything.
You can try to decrease the CPU and memory resources in Docker Desktop, although I don’t think it is likely to be a problem. But I also don’t know AWS VPN. If for any reason the VPN doesn’t have aneough resources, that could also cause a crash. You can find the CPU and memory settings in “Resources » Advanced”.
You can disable Automatic software updates in “Software updates” just to test if it sends any incompatible package. You can go to the “Notifications” menu and disable notifications, because some of those could be notifications based on data downloaded from the internet.