https://bugzilla.redhat.com/show_bug.cgi?id=1166950
--- Comment #4 from Daniel Walsh <dwalsh(a)redhat.com> ---
We have fixed the latest docker to label these volumes correctly. And changed
SELinux to block writing to docker_var_lib_t. Since most content under
/var/lib/docker is docker_var_lib_t, it is pretty dangerous to allow containers
to write any where under that directory.
Michael, if you go to /var/lib/docker/vfs you could probably just run chcon
there
chcon -r -t svirt_sandbox_file_t .
And that will fix your problem. I guess I could change the default policy to
set that label.
--
You are receiving this mail because:
You are on the CC list for the bug.