[golang-github-openshift-go-systemd/el6] not needed on el6
by Lokesh Mandvekar
commit c07f339750511b98094b8ae91daabf77a4e9ae31
Author: Lokesh Mandvekar <lsm5(a)fedoraproject.org>
Date: Wed Sep 17 05:21:31 2014 -0500
not needed on el6
.gitignore | 1 -
dead.package | 1 +
golang-github-openshift-go-systemd.spec | 60 -------------------------------
sources | 1 -
4 files changed, 1 insertions(+), 62 deletions(-)
---
diff --git a/dead.package b/dead.package
new file mode 100644
index 0000000..0f308f9
--- /dev/null
+++ b/dead.package
@@ -0,0 +1 @@
+not needed on el6
9 years, 7 months
[Bug 1141507] New: /etc/resolv.conf inaccessible with --selinux-enabled
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1141507
Bug ID: 1141507
Summary: /etc/resolv.conf inaccessible with --selinux-enabled
Product: Fedora
Version: rawhide
Component: docker-io
Assignee: lsm5(a)fedoraproject.org
Reporter: lsm5(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jperrin(a)centos.org,
lsm5(a)fedoraproject.org, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
Don't think this condition existed at the time of docker 1.2.0 update (though I
could be wrong).
HOST
$ cat /etc/sysconfig/docker
OPTIONS=--selinux-enabled
CONTAINER
bash-4.2# ls -aZ /etc/resolv.conf
ls: cannot access /etc/resolv.conf: Permission denied
---------------------------------
HOST
$ cat /etc/sysconfig/docker
OPTIONS=
CONTAINER
bash-4.2# ls -aZ /etc/resolv.conf
-rw-r--r--. root root system_u:object_r:docker_var_lib_t:s0 /etc/resolv.conf
NVRs:
$ rpm -q docker-io
docker-io-1.2.0-2.fc22.x86_64
$ rpm -q selinux-policy
selinux-policy-3.13.1-81.fc22.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 7 months
[Bug 1069718] New: Kernel container scalability issue in docker - VFS and mount path consuming too much CPU
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1069718
Bug ID: 1069718
Summary: Kernel container scalability issue in docker - VFS and
mount path consuming too much CPU
Product: Red Hat Enterprise Linux 7
Version: 7.0
Component: systemd
Severity: urgent
Priority: urgent
Assignee: systemd-maint(a)redhat.com
Reporter: sct(a)redhat.com
QA Contact: qe-baseos-daemons(a)redhat.com
CC: agk(a)redhat.com, alexl(a)redhat.com, fs-maint(a)redhat.com,
fweimer(a)redhat.com, golang(a)lists.fedoraproject.org,
ikent(a)redhat.com, jeder(a)redhat.com,
jpoimboe(a)redhat.com, lsm5(a)redhat.com,
lvm-team(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, mjenner(a)redhat.com,
perfbz(a)redhat.com, rwheeler(a)redhat.com,
skottler(a)redhat.com, vbatts(a)redhat.com
Depends On: 1061359, 1064929
Group: private
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1061359
[Bug 1061359] improve docker devicemapper backend scalability
https://bugzilla.redhat.com/show_bug.cgi?id=1064929
[Bug 1064929] Kernel container scalability issue in docker - VFS and mount
path consuming too much CPU
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 7 months