RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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.

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

Does not look like there was any movement on this?

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).