Cannot connect to container after setup #31
Comments
|
Docker Engine: |
% docker run --rm --privileged --pid=host debian nsenter -t 1 -m -u -n -i iptables-save
nsenter: failed to execute iptables-save: No such file or directory |
|
@normtown if you check the README, there is an additional note under the command you're using Can you try this command instead? Then attempt to ping the container? I keep all the latest wrappings for this system within the nodejs docker helpers package I created |
|
Thanks for that clarification. I ran the command. There were no error messages, but also still no change in behavior. My laptop shell still cannot connect to On a side note, it wasn't clear to me that I needed to run that command because the README says:
I read that as neither command (above or below) being necessary when running a version greater than 17.12.0. In my case, I'm running 18.09.2. |
|
so to clarify you followed these steps:
let me know if the above helps in any way P.S. Also check this issue for a list of information you can provide me to help debug the issue: #11 Example docker-compose file: |
|
@normtown any update on this? |
I really don't get why this is not working. I'm simply running a netcat listener in my container:
...and trying to connect from my laptop's shell, which fails:
Before doing this test, I had set up a route on my laptop that uses the
10.0.75.2gateway:...which we can see here:
We can see the
tap1virtual device is present on the laptop:...and we can see the network devices in the container here:
% docker run --rm --net=host --privileged alpine ifconfig docker0 Link encap:Ethernet HWaddr 02:42:CC:10:A0:EF inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0 inet6 addr: fe80::42:ccff:fe10:a0ef/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:828 (828.0 B) eth0 Link encap:Ethernet HWaddr 02:50:00:00:00:01 inet addr:192.168.65.3 Bcast:192.168.65.255 Mask:255.255.255.0 inet6 addr: fe80::50:ff:fe00:1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:978 errors:0 dropped:0 overruns:0 frame:0 TX packets:986 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:100738 (98.3 KiB) TX bytes:80543 (78.6 KiB) eth1 Link encap:Ethernet HWaddr 00:A0:98:BC:F5:D7 inet addr:10.0.75.2 Bcast:10.0.75.3 Mask:255.255.255.252 inet6 addr: fe80::2a0:98ff:febc:f5d7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4616 errors:0 dropped:0 overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1419346 (1.3 MiB) TX bytes:1138 (1.1 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:140 (140.0 B) TX bytes:140 (140.0 B)Hyperkit appears to be running with the
tap1device passed to it:One thing that seems a little odd to me is that bus 2 has both a "hard disk" on it (
ahci-hd) and the tap device that was injected by the shim script (virtio-tap). The script seems to assume that anything on bus 2 is a network device. I'm curious why that is the case.Interestingly, the laptop cannot connect to the host VM either. I can get a shell with
screen:% screen ~/Library/Containers/com.docker.docker/Data/vms/0/ttyHere's
ifconfigfrom the host VM:And I run a netcat listener in the host VM:
...with the same result when I try to connect from the Mac shell:
For completeness, here's the rest of any debug info I can think of giving.
The route table on the host VM:
And the tuntap devices installed on the Mac:
The text was updated successfully, but these errors were encountered: