-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
container network unreacheable #104
Comments
Should I run some commands on the container or on the host to provide you with more information? |
Please generate Technical Report in Parallels Desktop and post its id here. |
Technical ID 373236368 |
And 373237626 |
I doubt guest kernel panic may have something to do with Cisco Any Connect running on host. But Any Connect may spoil routing: it may add routes to VPN which overwrite routes to virtual machines–check this out. Or drop output of |
@romankulikov Setting shared network to 172.16.1 helped me with the issue. Thanks! |
docker container ip is 10.211.55.3
some time, after up, i see next:
and a i do not ping from host to container
but i can ping from container to host
The text was updated successfully, but these errors were encountered: