docker.io host name resolution fails after switching networks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
docker.io (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When switching networks, docker.io (1.0.1~
In the following example, 99.99.99.99 is a placeholder for the DNS server address in the network the notebook was connected to previously. This IP is not mentioned in /etc/resolv.conf anymore. From the current network, this IP is not reachable.
$ docker build some-image
Sending build context to Docker daemon 4.096 kB
Sending build context to Docker daemon
Step 0 : FROM ubuntu:utopic
Pulling repository ubuntu
2014/10/30 21:55:00 Get https:/
make: *** [all] Error 1
Expected behavior: docker should be automatically notified when /etc/resolv.conf changes, and use the appropriate DNS server for the network we're currently connected to.
Workaround:
$ sudo service docker.io restart
docker.io stop/waiting
docker.io start/running, process 2369
$ docker build some-image
Sending build context to Docker daemon 4.096 kB
Sending build context to Docker daemon
Step 0 : FROM ubuntu:utopic
Pulling repository ubuntu
277eb4304907: Download complete
511136ea3c5a: Download complete
[...]
Is this still a problem?