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

Unable to resolve internal IPs #122

Closed
mfriedenhagen opened this issue Apr 28, 2016 · 2 comments
Closed

Unable to resolve internal IPs #122

mfriedenhagen opened this issue Apr 28, 2016 · 2 comments

Comments

@mfriedenhagen
Copy link

Hello,

docker-machine ssh xhyve  
                        ##         .
                  ## ## ##        ==
               ## ## ## ## ##    ===
           /"""""""""""""""""\___/ ===
      ~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ /  ===- ~~~
           \______ o           __/
             \    \         __/
              \____\_______/
 _                 _   ____     _            _
| |__   ___   ___ | |_|___ \ __| | ___   ___| | _____ _ __
| '_ \ / _ \ / _ \| __| __) / _` |/ _ \ / __| |/ / _ \ '__|
| |_) | (_) | (_) | |_ / __/ (_| | (_) | (__|   <  __/ |
|_.__/ \___/ \___/ \__|_____\__,_|\___/ \___|_|\_\___|_|
Boot2Docker version 1.11.1, build HEAD : 7954f54 - Wed Apr 27 16:36:45 UTC 2016
Docker version 1.11.1, build 5604cbe
docker@boot2docker:~$ cat /etc/resolv.conf 
nameserver 192.168.64.1
docker@boot2docker:~$ ifconfig 
docker0   Link encap:Ethernet  HWaddr 02:42:34:54:D8:97  
          inet addr:169.254.0.1  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::42:34ff:fe54:d897/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1129 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1406 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:127674 (124.6 KiB)  TX bytes:1687993 (1.6 MiB)

eth0      Link encap:Ethernet  HWaddr 6A:39:BF:60:CF:32  
          inet addr:192.168.64.4  Bcast:192.168.64.255  Mask:255.255.255.0
          inet6 addr: fe80::6839:bfff:fe60:cf32/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:292670 errors:0 dropped:0 overruns:0 frame:2060
          TX packets:116225 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:375179849 (357.7 MiB)  TX bytes:8184957 (7.8 MiB)

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:32 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:2752 (2.6 KiB)  TX bytes:2752 (2.6 KiB)

veth91353e4 Link encap:Ethernet  HWaddr 42:DD:26:1A:2D:2D  
          inet6 addr: fe80::40dd:26ff:fe1a:2d2d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1129 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1414 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:143480 (140.1 KiB)  TX bytes:1688641 (1.6 MiB)

The resolver is not able to resolve our internal IPs out the box. After a restart I have to add our internal DNS-server manually in /etc/resolv.conf.

After that I am able to pull images from our internal registry 😁

@Strech
Copy link

Strech commented Apr 29, 2016

@mfriedenhagen I have the same problem while using VPN. This problem solved here machyve/xhyve#84 you should allow your host bridge to use your internal network

@mfriedenhagen
Copy link
Author

Probably fixed after 4 years

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

No branches or pull requests

3 participants