Red Hat Bugzilla – Bug 1259342
docker: Fail to start if selinux is enabled and overlayfs is being used as graph driver
Last modified: 2016-04-01 10:25:06 EDT
Description of problem:
Currently overlayfs does not work with selinux. By default selinux is enabled and if user chooses to use overlay as graph driver, there will be issues.
Modify docker so that it detects this situation during start and fails with appropriate error message.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Sally we already do this for BTRFS, you should just search the code and make the same change.
sally, has it been merged into docker we ship in rhel? MODIFIED flag means that patch has been committed in the source tree of redhat rpm.
Or rather, an rpm build has been done and rpm is available for testing. Then we will call it MODIFIED.
Sorry for the confusion! Dan also pointed out my misuse of 'MODIFIED'..
Now I know :)
Fixed in docker-1.9
# docker daemon --storage-driver=overlay
INFO Firewalld running: false
INFO Default bridge (docker0) is assigned with an IP address 172.17.0.1/16. Daemon option --bip can be used to set a preferred IP address
# docker daemon --selinux-enabled --storage-driver=overlay
FATA Error starting daemon: SELinux is not supported with the overlay graph driver
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.