Bug 1448331

Summary:	Docker fails to start container without /etc/resolv.conf
Product:	Red Hat Enterprise Linux 7	Reporter:	Stef Walter <stefw>
Component:	docker	Assignee:	Antonio Murdaca <amurdaca>
Status:	CLOSED CURRENTRELEASE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	amurdaca, dwalsh, lsm5, mpitt
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-25 06:11:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stef Walter 2017-05-05 08:44:18 UTC

Description of problem:

The Docker command fails to start without /etc/resolv.conf. A lack of /etc/resolv.conf often occurs on network isolated systems, such as testing systems that aim to produce reliable results. 

Version-Release number of selected component (if applicable):

docker-1.12.6-16.el7.x86_64

How reproducible:

Every time.

Steps to Reproduce:
1. # systemctl start docker
2. # docker pull busybox
3. # rm -f /etc/resolv.conf
4. # docker run -ti busybox /bin/bash

Actual results:

/usr/bin/docker-current: Error response from daemon: open /etc/resolv.conf: no such file or directory.

Expected results:

A shell prompt in the container.

Comment 2 Stef Walter 2017-05-05 08:45:07 UTC

This bug was caught by the Cockpit Integration tests. We are putting them on an isolated network, and this is one of the issues encountered.

Comment 3 Antonio Murdaca 2017-05-05 09:19:11 UTC

Reopened an old issue asking for information upstream https://github.com/moby/moby/issues/4861#issuecomment-299419368

Comment 4 Daniel Walsh 2017-06-30 16:00:00 UTC

Does not look like there was any movement on this?

Comment 5 Martin Pitt 2018-04-25 06:11:51 UTC

I think this can be closed now. I verified that this isn't a problem on RHEL 7.5 or Fedora 26 any more. (Also, see https://github.com/cockpit-project/cockpit/pull/9040).