No connetion in docker #44

Closed
opened 2025-12-28 23:22:28 +01:00 by adam · 6 comments
Owner

Originally created by @tobiasreichel on GitHub (Jun 20, 2020).

Little Problem i have no connetion inside docker
container is connected to the default bridge network
but no connetion
any hint why?

Originally created by @tobiasreichel on GitHub (Jun 20, 2020). Little Problem i have no connetion inside docker container is connected to the default bridge network but no connetion any hint why?
adam closed this issue 2025-12-28 23:22:28 +01:00
Author
Owner

@sickcodes commented on GitHub (Jun 20, 2020):

We are using user-mode networking.

https://github.com/sickcodes/Docker-OSX/blob/master/Dockerfile#L162

Not attached to the bridge. Unless you are referring to the Docker container's bridge, which is a Docker issue.

Did you update to latest version?

docker pull sickcodes/docker-osx

@sickcodes commented on GitHub (Jun 20, 2020): We are using user-mode networking. https://github.com/sickcodes/Docker-OSX/blob/master/Dockerfile#L162 Not attached to the bridge. Unless you are referring to the Docker container's bridge, which is a Docker issue. Did you update to latest version? `docker pull sickcodes/docker-osx`
Author
Owner

@sickcodes commented on GitHub (Jun 20, 2020):

If that fixed it, feel free to close the issue :)

@sickcodes commented on GitHub (Jun 20, 2020): If that fixed it, feel free to close the issue :)
Author
Owner

@jviotti commented on GitHub (Jun 23, 2020):

@sickcodes I'm facing the same issue, and the latest version didn't help. I'm running on Fedora 32 if that makes a difference, and the host has both ethernet & wifi.

The host ifconfig is:

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:a5ff:fe92:4b54  prefixlen 64  scopeid 0x20<link>
        ether 02:42:a5:92:4b:54  txqueuelen 0  (Ethernet)        
        RX packets 95  bytes 6008 (5.8 KiB)                                              
        RX errors 0  dropped 0  overruns 0  frame 0      
        TX packets 97  bytes 10880 (10.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.18  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::d417:8baa:b73e:1c6c  prefixlen 64  scopeid 0x20<link>
        ether 94:c6:91:a1:aa:f8  txqueuelen 1000  (Ethernet)
        RX packets 2911437  bytes 4410556906 (4.1 GiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 1541719  bytes 219756431 (209.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xdc300000-dc320000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 32  bytes 3017 (2.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 32  bytes 3017 (2.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethca3ed2e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::889:2bff:fe5d:4dc  prefixlen 64  scopeid 0x20<link>
        ether 0a:89:2b:5d:04:dc  txqueuelen 0  (Ethernet)
        RX packets 95  bytes 7338 (7.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 116  bytes 13176 (12.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:2b:c9:c6  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp58s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.19  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::d510:10a9:96de:5fba  prefixlen 64  scopeid 0x20<link>
        ether 14:4f:8a:36:c3:c9  txqueuelen 1000  (Ethernet)
        RX packets 109502  bytes 7701068 (7.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 157  bytes 16758 (16.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

And the macOS VM says:

Screen Sharing Picture 23 June 2020 at 15 59 34 BST

@jviotti commented on GitHub (Jun 23, 2020): @sickcodes I'm facing the same issue, and the latest version didn't help. I'm running on Fedora 32 if that makes a difference, and the host has both ethernet & wifi. The host `ifconfig` is: ``` docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 inet6 fe80::42:a5ff:fe92:4b54 prefixlen 64 scopeid 0x20<link> ether 02:42:a5:92:4b:54 txqueuelen 0 (Ethernet) RX packets 95 bytes 6008 (5.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 97 bytes 10880 (10.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.18 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::d417:8baa:b73e:1c6c prefixlen 64 scopeid 0x20<link> ether 94:c6:91:a1:aa:f8 txqueuelen 1000 (Ethernet) RX packets 2911437 bytes 4410556906 (4.1 GiB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 1541719 bytes 219756431 (209.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0xdc300000-dc320000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 32 bytes 3017 (2.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 32 bytes 3017 (2.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethca3ed2e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::889:2bff:fe5d:4dc prefixlen 64 scopeid 0x20<link> ether 0a:89:2b:5d:04:dc txqueuelen 0 (Ethernet) RX packets 95 bytes 7338 (7.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 116 bytes 13176 (12.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:2b:c9:c6 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp58s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.19 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::d510:10a9:96de:5fba prefixlen 64 scopeid 0x20<link> ether 14:4f:8a:36:c3:c9 txqueuelen 1000 (Ethernet) RX packets 109502 bytes 7701068 (7.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 157 bytes 16758 (16.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` And the macOS VM says: ![Screen Sharing Picture 23 June 2020 at 15 59 34 BST](https://user-images.githubusercontent.com/2192773/85420020-9d64a100-b56a-11ea-9ca7-ec3577da69b9.png)
Author
Owner

@jviotti commented on GitHub (Jun 23, 2020):

I started the VM using this command:

docker run -e RAM=6 --privileged -p 50922:10022 -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix docker-osx:latest

Which as far as I understand should have opened port 50922 on the host, but that didn't happen either.

@jviotti commented on GitHub (Jun 23, 2020): I started the VM using this command: ``` docker run -e RAM=6 --privileged -p 50922:10022 -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix docker-osx:latest ``` Which as far as I understand should have opened port 50922 on the host, but that didn't happen either.
Author
Owner

@jviotti commented on GitHub (Jun 23, 2020):

It seems to work if I run it like this:

docker run --privileged --net host -e "DISPLAY=${DISPLAY:-:0.0}" -e RAM=6 --cap-add=ALL -v /tmp/.X11-unix:/tmp/.X11-unix -v /dev:/dev -v /lib/modules:/lib/modules  -v /var/run/libvirt/libvirt-sock:/var/run/libvirt/libvirt-sock docker-osx:latest
@jviotti commented on GitHub (Jun 23, 2020): It seems to work if I run it like this: ``` docker run --privileged --net host -e "DISPLAY=${DISPLAY:-:0.0}" -e RAM=6 --cap-add=ALL -v /tmp/.X11-unix:/tmp/.X11-unix -v /dev:/dev -v /lib/modules:/lib/modules -v /var/run/libvirt/libvirt-sock:/var/run/libvirt/libvirt-sock docker-osx:latest ```
Author
Owner

@sickcodes commented on GitHub (Jun 24, 2020):

Great to hear it works :)

@sickcodes commented on GitHub (Jun 24, 2020): Great to hear it works :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Docker-OSX#44