Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:
https://github.com/docker/docker/issues/17190

Docker 1.8 has a race condition and can corrupt /etc/hosts inside a container 

Google is coordinating a temp fix for the distros since upstream is pushing the issue out to upstream 1.9 for a fix.


Expected results:


Additional info:

As soon as they have a fix, we can patch this, but I am not sure if we are releasing anything before we ship docker-1.9?

Looks like googles fix will be outside of docker.

So we can say this is partially fixed in docker-1.9. With more fixes coming in docker-1.10.

Fixed in docker-1.10

In docker-1.9.1-15.el7.x86_64,
use this https://github.com/docker/docker/issues/17190#issuecomment-149437458,
the file looks good
# docker exec test-master cat /etc/hosts
172.17.0.2	f988d8d83483
127.0.0.1	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters

i'm moving this back to MODIFIED as per Dan's comment and scheduling this for 1.10 update.

changing component to docker-latest

It works well on docker-latest-1.10.3-19, so moving the bug to VERIFIED status.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-1057.html