Bug 1273598
| Summary: | docker looses /etc/hosts | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Subhendu Ghosh <sghosh> |
| Component: | docker-latest | Assignee: | Lokesh Mandvekar <lsm5> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.1 | CC: | ajia, ghelleks, lsm5, lsu, royoung |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-12 14:54:09 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1303656, 1305185 | ||
|
Description
Subhendu Ghosh
2015-10-20 18:40:48 UTC
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 |