Repository: boot2docker/boot2docker

Issue #357: boot2docker 0.8.1 on OS X: container DNS stuck on 8.8.8.8, 8.8.4.4
Created: 2014-05-14T06:25:13Z
My containers no longer reliably pick up my current DNS servers.
Check current settings:
$ cat /etc/resolv.conf
search internal1.example.com internal2.example.com internal3.example.com
nameserver 10.10.10.10
nameserver 10.11.10.11

Bounce boot2docker, as I've become accustomed to doing after VPN changes:
$ boot2docker down
[2014-05-14 16:06:39] Shutting down boot2docker-vm...

$ boot2docker up
[2014-05-14 16:06:44] Starting boot2docker-vm...
[2014-05-14 16:07:09] Started.

To connect the docker client to the Docker daemon, please set:
export DOCKER_HOST=tcp://localhost:4243

Check DNS settings on boot2docker-vm:
$ boot2docker ssh
docker@localhost's password: 
                        ##        .
                  ## ## ##       ==
               ## ## ## ##      ===
           /""""""""""""""""\___/ ===
      ~~~ {~~ ~~~~ ~~~ ~~~~ ~~ ~ /  ===- ~~~
           \______ o          __/
             \    \        __/
              \____\______/
 _                 _   ____     _            _
| |__   ___   ___ | |_|___ \ __| | ___   ___| | _____ _ __
| '_ \ / _ \ / _ \| __| __) / _` |/ _ \ / __| |/ / _ \ '__|
| |_) | (_) | (_) | |_ / __/ (_| | (_) | (__|   <  __/ |
|_.__/ \___/ \___/ \__|_____\__,_|\___/ \___|_|\_\___|_|
boot2docker: 0.8.1
             master : 17bb8c2 - Thu May  8 02:55:10 UTC 2014
docker@boot2docker:~$ cat /etc/resolv.conf
search internal1.example.com
nameserver 10.10.10.10
nameserver 10.11.10.11

The two nameserver entries are OK, but two of the three search domains vanished.
Ensure the docker process doesn't have DNS settings:
docker@boot2docker:~$ ps auxw|grep docker
  607 root     /usr/local/bin/docker -d -D -g /var/lib/docker -H unix:// -H tcp://0.0.0.0:4243

Good. So, the container should get the name servers we saw earlier, right?
$ docker run --rm -t -i ubuntu:precise cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
search internal1.example.com

Nope. We're still on one of three search domains, and both nameserver entries have been replaced. I can't figure out where those defaults came from, either. Maybe if we check OS X' alternatives?
$ scutil --dns | grep 8.8 | wc -l
       0

Not a sausage.
Ensure versions are recent:
$ docker version
Client version: 0.11.1
Client API version: 1.11
Go version (client): go1.2.1
Git commit (client): fb99f99
Server version: 0.11.1
Server API version: 1.11
Git commit (server): fb99f99
Go version (server): go1.2.1
Last stable version: 0.11.1

Yep. So, I can't upgrade my way out of the problem.
Any ideas?
I can't work around this with docker run --dns, as I need correct DNS resolution for docker build to work and it doesn't accept --dns.

Duplicate issue #408: no DNS servers
Created: 2014-06-24T21:25:20Z
I have made the standard Boot2docker installation for mac (with the package).
I still have the default configuration and
When I do  :
docker pull mbentley/debian-php5-fpm
Pulling repository mbentley/debian-php5-fpm
2014/06/24 22:57:33 Get https://index.docker.io/v1/repositories/mbentley/debian-php5-fpm/images: dial tcp: lookup index.docker.io: no DNS servers
I have no DNS servers in resolv.conf in boot2docker VM.
And When I put one and reboot the VM it disappear.

Closing comment (2014-06-25T02:34:39Z): might be related to #357
this is one of those painful things that are hard for me to find, reproduce and then work out if its fixed or not.
thankyou for the info :)