| Summary: | [extras-rhel-7.2.7] Docker storage setup should detect overlay2 driver correctly | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vivek Goyal <vgoyal> |
| Component: | docker-latest | Assignee: | Lokesh Mandvekar <lsm5> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | unspecified | Docs Contact: | Yoana Ruseva <yruseva> |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | bbreard, lsu, qcai, yruseva |
| Target Milestone: | rc | Keywords: | Documentation, Extras, FutureFeature, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | docker-latest-1.12.0-11.el7 | Doc Type: | Technology Preview |
| Doc Text: |
overlay2 storage driver now available
The overlay2 graph driver, along with overlay, is an implementation of OverlayFS, a copy-on-write union file system that features page-cache sharing between containers. However, overlay2 is the more performant option. Currently, the driver requires SELinux to be disabled in docker. overlay2 is available for docker as a Technology Preview feature.
To enable the driver, specify *overlay2* in the _/etc/sysconfig/docker-storage/setup_ file:
STORAGE_DRIVER=overlay2
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-15 08:29:44 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: | |
|
Description
Vivek Goyal
2016-08-22 19:03:29 UTC
Vivek, could you please fill out rel-notes Doc Text for this? Hi, I updated the Doc Text and included it in the Release Notes as a Technology Preview.Can someone have a look at the text and see if we can improve it. At the moment it doesn't contain much detailed information. 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/RHBA-2016-1829.html |