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 1447455 - overlay2 broken on docker-latest
Summary: overlay2 broken on docker-latest
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker-latest
Version: 7.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-02 20:51 UTC by Qian Cai
Modified: 2017-05-26 14:55 UTC (History)
6 users (show)

Fixed In Version: docker-latest-1.13.1-7.git475c5d2.el7_3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-26 14:55:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1330 0 normal SHIPPED_LIVE docker-latest bug fix and enhancement update 2017-05-26 18:14:56 UTC

Description Qian Cai 2017-05-02 20:51:05 UTC
Description of problem:
Unable to use overlay2 driver in docker-latest anymore in RHEL 7.3.4.

May 02 20:12:35 caiqian-jmaster.localdomain dockerd-latest[31552]: time="2017-05-02T20:12:35.902550200Z" level=info msg="libcontainerd: new containerd process, pid: 31563"
May 02 20:12:36 caiqian-jmaster.localdomain dockerd-latest[31552]: Error starting daemon: error initializing graphdriver: driver not supported

The workaround is to add EXTRA_DOCKER_STORAGE_OPTIONS="--storage-opt overlay2.override_kernel_check=true" in /etc/sysconfig/docker-latest-storage-setup

Almost certain this is also broken in RHEL7.4.

Version-Release number of selected component (if applicable):
docker-latest-1.13.1-4.el7.x86_64
kernel-3.10.0-514.16.1.el7.x86_64

How reproducible:
always

Comment 1 Vivek Goyal 2017-05-02 21:01:05 UTC
Is it regression? So it works with docker-1.12? If yes, that means we are carrying some patch in docker-1.12 which we dropped on floor for docker-1.13. Let me check.

Comment 5 Antonio Murdaca 2017-05-03 08:20:25 UTC
Fixed in projectatomic/docker branches:

docker-1.13.1
docker-1.13.1-rhel

Comment 8 Luwen Su 2017-05-16 09:20:50 UTC
#service docker-latest status -l
active (running) since Tue 2017-05-16 17:19:18 CST; 5s ago
 ├─7792 /usr/bin/dockerd-latest *****  --storage-driver overlay2 

# rpm -q docker-latest kernel
docker-latest-1.13.1-10.git475c5d2.el7.x86_64
kernel-3.10.0-470.el7.x86_64

Comment 10 errata-xmlrpc 2017-05-26 14:55:10 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-2017:1330


Note You need to log in before you can comment on or make changes to this bug.