Skip to content
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

Open
santarinto opened this issue Jul 1, 2021 · 6 comments
Open

container network unreacheable #104

santarinto opened this issue Jul 1, 2021 · 6 comments

Comments

@santarinto
Copy link

docker container ip is 10.211.55.3

some time, after up, i see next:

 docker-machine ls
NAME   ACTIVE   DRIVER      STATE     URL   SWARM   DOCKER   ERRORS
dms             parallels   Timeout

and a i do not ping from host to container

ping 10.211.55.3
PING 10.211.55.3 (10.211.55.3): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
^C
--- 10.211.55.3 ping statistics ---
6 packets transmitted, 0 packets received, 100.0% packet loss

but i can ping from container to host

image

@santarinto
Copy link
Author

Should I run some commands on the container or on the host to provide you with more information?

@romankulikov
Copy link
Collaborator

Please generate Technical Report in Parallels Desktop and post its id here.

@santarinto
Copy link
Author

Technical ID 373236368

@santarinto
Copy link
Author

And 373237626
I think that the kernel panic is connected with the fact that I have cisco any connect running

@romankulikov
Copy link
Collaborator

romankulikov commented Jul 31, 2021

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 netstat -nr here. That kind of problem could be workarounded by setting subnet for Shared network to 172.16.1 in Parallels Desktop configuration.

@esmirnov
Copy link

@romankulikov Setting shared network to 172.16.1 helped me with the issue. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants