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.
Bug 1475625 - Change the default storage driver to overlay2
Summary: Change the default storage driver to overlay2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Frantisek Kluknavsky
QA Contact: atomic-bugs@redhat.com
Maxim Svistunov
URL:
Whiteboard:
Depends On:
Blocks: 1186913 1477926
TreeView+ depends on / blocked
 
Reported: 2017-07-27 03:03 UTC by Ben Breard
Modified: 2019-03-20 05:24 UTC (History)
12 users (show)

Fixed In Version: container-storage-setup-0.9.0-1.rhel75.gite0997c3.el7
Doc Type: Release Note
Doc Text:
Default storage driver for docker has switched to ovlerlay2 (from devicemapper) in RHEL7.5. So new docker installations should see overlay2 as default on RHEL7.5 or newer releases. On older releases, devicemapper still continues to be the default. Upgrade of existing installations should remain unaffected.
Clone Of:
Environment:
Last Closed: 2018-04-10 23:59:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1064 0 None None None 2018-04-10 23:59:15 UTC

Description Ben Breard 2017-07-27 03:03:08 UTC 
Description of problem:

RHEL & Atomic Host default to devicemapper as the storage driver for docker. That needs to change to overlay2.

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


Actual results:


Expected results:


Additional info:

I couldn't find another tracker for this. Please close if one already exists.
Comment 3 Ben Breard 2017-08-09 18:34:02 UTC 
We need to look out for older RHEL 7 systems, pre 7.3, where the file system is missing "type=1" with XFS. One option would be putting a check in the unit file that would fail to start if "type=0" is found for the file system under /var/lib/docker. container-storage-setup will also need checks for this.
Comment 4 Daniel Walsh 2017-08-11 12:25:18 UTC 
c
Comment 5 Vivek Goyal 2017-10-24 20:49:41 UTC 
Dan, lokesh, it might be time to discuss this and make related changes. We have another similar bug for atomic host here.

https://bugzilla.redhat.com/show_bug.cgi?id=1505621


Lets us keep all the conversation about all the flavors of rhel 7.5 in this bz and how their defaults storage config files should look like here.
Comment 7 Vivek Goyal 2017-10-24 21:06:18 UTC 
So in fedora, we have 4 variants. Atomic.host, Cloud, Server and Workstation and we have per product configuration.

How many do we have in RHEL. And then we can discuss per product configuration of each product.

On atomic, I have assuming that rootfs size is by default small (3G). If that's the case we should probably setup overlayfs on a separate volume from root volume group.

For others I am assuming that by default rootfs partition is big and overlayfs should be setup on rootfs. (And not a separate volume). Anyway, for cloud images, there might not be any volume group so setting it up on rootfs might be the only option.

I guess we also will have to check ftype and fall back to device mapper if rootfs does not have ftype=1.
Comment 8 Vivek Goyal 2017-10-30 13:51:16 UTC 
Lokesh, can you please take care of making spec file changes for this. Dan mentioned that we don't have any product variants. So we could probably just have another docker-storage.sysconfig for overlay and install that. 

We need to make sure that we check rhel version and do this change only for 7.5 onwards. (And not for 7.3 and 7.4)

Also we will have to ftype check also and make sure rootfs supports ftype=1
Comment 9 Vivek Goyal 2017-10-31 14:56:51 UTC 
Ok, had an IRC conversation with walters just now about what's planned for 7.5 atomic. They are planning that rootfs will grow automatically to consume all the free space in root volume group. (like F27AH). 

If that's the case, then we don't have to setup a separate volume for overlay in atomic host. And we can create a default config which works across all rhel 7.5 products.

I think something as simple as following should work.

# cat /etc/sysconfig/docker-storage-setup
STORAGE_DRIVER=overlay2
Comment 10 Dusty Mabe 2017-10-31 15:27:05 UTC 
We should probably make sure we have some good documentation somewhere that shows the user how to set up a separate LV for container root (using container-storage-setup) that will use overlay2 on top.
Comment 11 Vivek Goyal 2017-10-31 15:32:17 UTC 
We cover this in "Managing Containers" guide.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/managing_containers/#using_the_overlay_graph_driver
Comment 12 Ben Breard 2017-10-31 15:34:29 UTC 
We cover it, but we could probably use a better example for AH.
Comment 24 errata-xmlrpc 2018-04-10 23:59:02 UTC 
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://access.redhat.com/errata/RHBA-2018:1064
Note You need to log in before you can comment on or make changes to this bug.