https://bugzilla.redhat.com/show_bug.cgi?id=1214394
Bug ID: 1214394
Summary: docker-io makes the hosts /sys directory read only
Product: Fedora
Version: rawhide
Component: docker-io
Severity: medium
Assignee: ichavero(a)redhat.com
Reporter: pwebster(a)ca.ibm.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
I installed docker-io on RHEL 6.6. If I create a regular container, I
suddenly can no longer suspend my machine. I tracked it down to the /sys
directory being mounted read-only on the host. Bug 1094198 says that it should
be mounted read-only within the container if the container is run as
non-privileged, but that should not effect the host.
Version-Release number of selected component (if applicable):
docker-io-1.4.1-3.el6.x86_64
RHEL 6.6
kernel-2.6.32-504.12.2.el6.x86_64
How reproducible: 100%
Steps to Reproduce:
Start a docker container:
bash$ docker run -ti fedora:latest /bin/bash
Outside of docker, run as root:
[root@wspwebster log]# echo 7 > /sys/module/cpufreq/parameters/debug
-bash: /sys/module/cpufreq/parameters/debug: Read-only file system
Actual results:
fails to write to /sys anymore. This effects other commands, like pm-suspend
(can't suspend my laptop anymore)
Expected results:
Should be able to write out to the /sys file system as root.
Additional info:
Version: Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
Version: G5ET90WW (2.50 )
Version: ThinkPad W530
--
You are receiving this mail because:
You are on the CC list for the bug.