Closed bullfly66 closed 2 years ago
me too
Sorry for the huge delay in response, this totally fell off my radar! 😧
Interestingly I'm not seeing the log output from the install_hyperkit_shim
in your example, which suggests that the installer thinks it's already installed. Only thing I can think to suggest is to attempt to uninstall the shim with the script below, and then try running install.sh
again and restarting docker when it prompts to do so.
mv -v /Applications/Docker.app/Contents/MacOS/com.docker.hyperkit{.real,}
mv -v /Applications/Docker.app/Contents/Resources/bin/hyperkit{.real,}
mv -v /Applications/Docker.app/Contents/Resources/bin/com.docker.hyperkit{.real,}
As an aside, I'm afraid I'm no longer in a position to be able to debug this to any greater extent, as (partly due to this docker limitation) the dev team I built this to support has moved over completely to linux and I no longer have access to a Mac on which to test it.
It's also possible that this fork by @remysaissy might be of interest as it looks like they've added a change to support newer versions of DfM which have moved the tty
used to bridge the tap device into the docker network.
My test result is that Failed to connect to container when i excecute
curl -I container_ip
I don't know what caused thisThank you
My list of steps: