Yuanhong Peng 10c88fc3ab Ignore "no such file" error when docker cannot find resolv.conf ...

`/etc/resolv.conf` is not an essential file in filesystem. (see
http://man7.org/linux/man-pages/man5/resolv.conf.5.html)

> If this file does not exist, only the name server on the local machine
> will be queried

It's baffling to users that containers can start with an empty
`resolv.conf` but cannot without this file.

This PR:
* ignore this error and use default servers for containers in `bridge`
  mode networking.
* create an empty resolv.conf in `/var/lib/docker/containers/<id>` in
  `host` mode networking.

Signed-off-by: Yuanhong Peng <pengyuanhong@huawei.com>

2017-08-22 10:20:44 +08:00

libnetwork

Ignore "no such file" error when docker cannot find resolv.conf

2017-08-22 10:20:44 +08:00

Description

No description provided

containersdockergogolang

546 MiB

Languages

Go 97.5%

Shell 1.2%

Dockerfile 0.6%

PowerShell 0.2%

Lua 0.2%

Other 0.1%