-
Notifications
You must be signed in to change notification settings - Fork 44
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
Timeouts after reboot #4
Comments
I have made some progress:
in this configuration container will get 2 ip addresses and it is routable only through the I also see that the routes are created correctly:
but pings on I tried disabling iptables in docker, but this did not help |
@ttyz Thanks for reaching out with your issue. I'm going to try to reproduce it on my end and then provide an update. |
Just an update, I was able to reproduce this using the following steps:
The fact that I will continue to dig and send updates as I make progress. |
Interestingly, pinging $ docker run --rm --net host wbitt/network-multitool ping 172.31.0.3
The directory /usr/share/nginx/html is not mounted.
Therefore, over-writing the default index.html file with some useful information:
WBITT Network MultiTool (with NGINX) - docker-desktop - 192.168.65.3 - HTTP: 80 , HTTPS: 443 . (Formerly praqma/network-multitool)
PING 172.31.0.3 (172.31.0.3) 56(84) bytes of data.
64 bytes from 172.31.0.3: icmp_seq=1 ttl=64 time=0.054 ms
64 bytes from 172.31.0.3: icmp_seq=2 ttl=64 time=0.086 ms
64 bytes from 172.31.0.3: icmp_seq=3 ttl=64 time=0.072 ms
64 bytes from 172.31.0.3: icmp_seq=4 ttl=64 time=0.086 ms
^C
--- 172.31.0.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3070ms
rtt min/avg/max/mdev = 0.054/0.074/0.086/0.013 ms |
I've determined the root cause of the problem. Packets from the macOS host going to the container through The solution is pretty simple, we just need to add an $ docker run --rm -it --net host --privileged wbitt/network-multitool iptables -t nat -A POSTROUTING -s 10.33.33.1 -j MASQUERADE I'll add in this logic shortly and let you know when that's done. |
I can confirm, everything now works as expected, thank you for your help 👍 |
I had everything setup and working but after a restart, I get requests timeout when trying to access the containers. Wireguard interface is up and accessible from host:
But containers are not:
The log does not show anything particularly interesting to me:
Can you maybe give me a hint on debugging the issue?
I am running Docker Desktop 4.3.2 (72729)
The text was updated successfully, but these errors were encountered: