Does the virtual network adapter exist both on the host and inside the VM? Did something cause the virtual network adapters to either lose their configuration (e.g IP address), get new information or be discarded entirely?
And also check the network settings from there. If you are having issues between the containers themselves, take a dive in to the setup of the VM (either the distro thats installed, or the hypervisor configuration) and check that the VM hasn't crashed, you haven't ran out of memory, storage, etc. Does it change when you lose the connection? In this case, something external is modifying the routing table, causing you to lose connection to the containers If you are having issues between the Mac and containers, but the containers communicate fine, take a look at the routing table that gets defined on the host. (And possibly some scripts to make it feel integrated in to the Mac system)Īre you having connection issues between the Mac and the containers, between the containers themselves or anything outside connecting in to the containers? If you are using an alternative setup to Docker Desktop, I'm assuming that it is the same setup, but with a different hypervisor. How it works under Mac is a Linux VM with the docker commands pointing to the instance inside the VM. When you say native docker under Mac, I'm assuming you mean Docker Desktop? AFAIK the Darwin kernel has no support for containers yet.
0 kommentar(er)
