[Bug 1094664] New: docker-io-0.10.0-2 disables access to /dev/shm
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1094664
Bug ID: 1094664
Summary: docker-io-0.10.0-2 disables access to /dev/shm
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: jpazdziora(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
While testing FreeIPA server and the 389 server in Docker container, I started
to see errors like Failed to create semaphore for stats file/Permission denied
with docker-io from updates-testing. Upon closer look, /dev/shm seems to be
mounted with 1755, which is different from what docker-io 0.9.1 does and what
you get on bare metal.
Version-Release number of selected component (if applicable):
docker-io-0.10.0-2.fc20.x86_64
How reproducible:
Deterministic.
Steps to Reproduce:
1. docker run -ti fedora:20 /bin/bash
2. In the container shell, run
mount | grep /dev/shm
ls -la /dev/shm
exit
3. Downgrade to docker-io-0.9.1 and repeat.
Actual results:
# docker run -ti fedora:20 /bin/bash
bash-4.2# mount | grep /dev/shm
shm on /dev/shm type tmpfs
(rw,nosuid,nodev,noexec,relatime,seclabel,size=65536k,mode=1755)
# docker run -ti fedora:20 /bin/bash
bash-4.2# ls -la /dev/shm
total 4
drwxrwxrwt. 2 root root 40 May 6 08:06 .
drwxr-xr-x. 4 root root 4096 May 6 08:06 ..
bash-4.2# exit
# rpm -q docker-io
docker-io-0.9.1-1.fc20.x86_64
# yum downgrade docker-io -y
[...]
# rpm -q docker-io
docker-io-0.9.1-1.fc20.x86_64
# docker run -ti fedora:20 /bin/bash
bash-4.2# mount | grep /dev/shm
shm on /dev/shm type tmpfs
(rw,nosuid,nodev,noexec,relatime,seclabel,size=65536k)
bash-4.2# ls -la /dev/shm
total 4
drwxrwxrwt. 2 root root 40 May 6 09:16 .
drwxr-xr-x. 4 root root 4096 May 6 09:16 ..
bash-4.2# exit
exit
#
Expected results:
Permissions on /dev/shm the same as on docker-io-0.9.1.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months
[Bug 1096123] New: useradd within EL6 container fails: failure while writing changes to /etc/passwd
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1096123
Bug ID: 1096123
Summary: useradd within EL6 container fails: failure while
writing changes to /etc/passwd
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: dcleal(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
Between docker-io-0.10.0-2.fc20 and docker-io-0.11.1-1.fc20, the following has
started failing:
$ docker run -t centos /usr/sbin/useradd test
useradd: failure while writing changes to /etc/passwd
'centos' is the official CentOS 6 image (0b443ba03958).
The Fedora 20 host has SELinux enforcing, and the same issue occurs when set to
permissive. No AVCs are seen.
Version-Release number of selected component (if applicable):
docker-io-0.11.1-1.fc20.x86_64
kernel-3.14.2-200.fc20.x86_64
How reproducible:
Always
Steps to Reproduce:
1. docker pull centos
2. docker run -t centos /usr/sbin/useradd test
Actual results:
useradd: failure while writing changes to /etc/passwd
Expected results:
no output
Additional info:
On 0.10.0, an strace of useradd shows:
open("/etc/group", O_RDONLY|O_CLOEXEC) = 11
fstat(11, {st_mode=S_IFREG|0644, st_size=379, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7feb5efe5000
read(11, "root:x:0:\nbin:x:1:bin,daemon\ndae"..., 4096) = 379
close(11) = 0
munmap(0x7feb5efe5000, 4096) = 0
fchown(10, 500, 12) = 0
fchmod(10, 0660) = 0
fsync(10) = 0
close(10) = 0
fstat(6, {st_mode=S_IFREG|0644, st_size=670, ...}) = 0
gettid() = 14
open("/proc/self/task/14/attr/fscreate", O_RDONLY) = 10
read(10, "", 4095) = 0
close(10) = 0
gettid() = 14
open("/proc/self/task/14/attr/fscreate", O_RDWR) = 10
write(10, "system_u:object_r:file_t:s0\0", 28) = 28
close(10) = 0
fstat(6, {st_mode=S_IFREG|0644, st_size=670, ...}) = 0
umask(077) = 022
open("/etc/passwd-", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 10
umask(022) = 077
lseek(6, 0, SEEK_SET) = 0
read(6, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 670
fstat(10, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7feb5efe5000
read(6, "", 4096) = 0
write(10, "root:x:0:0:root:/root:/bin/bash\n"..., 670) = 670
While on 0.11.1, strace shows:
open("/etc/group", O_RDONLY|O_CLOEXEC) = 10
fstat(10, {st_mode=S_IFREG|0644, st_size=379, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2905a38000
read(10, "root:x:0:\nbin:x:1:bin,daemon\ndae"..., 4096) = 379
close(10) = 0
munmap(0x7f2905a38000, 4096) = 0
fchown(9, 500, 12) = 0
fchmod(9, 0660) = 0
fsync(9) = 0
close(9) = 0
fstat(5, {st_mode=S_IFREG|0644, st_size=675, ...}) = 0
gettid() = 30
open("/proc/self/task/30/attr/fscreate", O_RDONLY) = 9
read(9, "", 4095) = 0
close(9) = 0
gettid() = 30
open("/proc/self/task/30/attr/fscreate", O_RDWR) = -1 EROFS (Read-only file
system)
write(2, "useradd: failure while writing c"..., 54useradd: failure while
writing changes to /etc/passwd
) = 54
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months
[Bug 1103323] New: docker on RHEL6.5 no longer needs to default to lxc
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1103323
Bug ID: 1103323
Summary: docker on RHEL6.5 no longer needs to default to lxc
Product: Fedora
Version: rawhide
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: vbatts(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
docker daemon on RHEL6 (and centos) is patched to launch with 'lxc' execdriver,
instead of the docker 'native' libcontainer
Version-Release number of selected component (if applicable):
$ docker version
Client version: 0.11.1
Client API version: 1.11
Go version (client): go1.2.1
Git commit (client): fb99f99/0.11.1
Server version: 0.11.1
Server API version: 1.11
Git commit (server): fb99f99/0.11.1
Go version (server): go1.2.1
Last stable version: 0.11.1
The reason we had mad this switch was due to the network bridge setup for
libcontainer had not worked correctly at first. This has since been fixed
upstream.
$ docker run -it fedora ping -c1 google.com
PING google.com (173.194.121.1) 56(84) bytes of data.
64 bytes from iad23s25-in-f1.1e100.net (173.194.121.1): icmp_seq=1 ttl=45
time=16.2 ms
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 16.294/16.294/16.294/0.000 ms
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months
[Bug 1087546] New: Request epel7 branch
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1087546
Bug ID: 1087546
Summary: Request epel7 branch
Product: Fedora EPEL
Version: epel7
Component: golang-github-coreos-go-systemd
Assignee: lsm5(a)redhat.com
Reporter: lsm5(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: bobbypowers(a)gmail.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com
Package Change Request
======================
Package Name: golang-github-coreos-go-systemd
New Branches: epel7
Owners: lsm5
InitialCC: golang-sig
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months
[Bug 1072041] New: Include a -devel that provides the docker source
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1072041
Bug ID: 1072041
Summary: Include a -devel that provides the docker source
Product: Fedora
Version: rawhide
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: vbatts(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, skottler(a)redhat.com,
vbatts(a)redhat.com
For client tooling, that uses internal packages of docker, the docker source
needs to available as a library.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months
[Bug 1102019] New: cannot remove /var/lib/docker just after a fresh install even when docker is stopped
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1102019
Bug ID: 1102019
Summary: cannot remove /var/lib/docker just after a fresh
install even when docker is stopped
Product: Fedora EPEL
Version: el6
Component: docker-io
Severity: medium
Priority: medium
Assignee: lsm5(a)redhat.com
Reporter: vdasgupt(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
Cannot remove /var/lib/docker just after a fresh install even when docker is
stopped. And even though the docker runtime root has been changed to
/home/docker and is no longer /var/lib/docker
# rmdir /var/lib/docker
rmdir: failed to remove `/var/lib/docker': Device or resource busy
lsof does not show anyone using this file/dir
Version-Release number of selected component (if applicable):
RHEL 6
Kernel 2.6.32-431.el6
Docker version 0.11.1, build fb99f99/0.11.1
Steps to Reproduce:
1. yum -y docker-io
2. service docker start ; service docker stop
3. add -g="/home/docker" to other_args in /etc/sysconfig/docker
4. service docker start ; service docker stop
5. checked that the docker runtime env files are now in /home/docker
6. Try to remove or rename /var/lib/docker and it does not allow
Actual results:
rmdir: failed to remove `/var/lib/docker': Device or resource busy
Expected results:
Should have removed or allowed to rename the directory
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months
[Bug 1098120] New: Unable to buid an run an image using sshd.
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1098120
Bug ID: 1098120
Summary: Unable to buid an run an image using sshd.
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: pantinor(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
Unable to succesfully build and run a fairly simple image that used to work.
Version-Release number of selected component (if applicable):
$ docker -v
Docker version 0.11.1, build fb99f99/0.11.1
How reproducible:
Always
Steps to Reproduce:
mkdir docker_test
cd docker_test
wget http://pastebin.com/raw.php?i=ie8BRcC4 -O Dockerfile
docker build -t sshd --no-cache
Actual results:
$ docker build -t sshd --no-cache .
Uploading context 2.56 kB
Uploading context
Step 0 : FROM centos
---> 539c0211cd76
Step 1 : RUN yum install -y openssh-server
---> Running in 65f28c081323
Loaded plugins: fastestmirror
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package openssh-server.x86_64 0:5.3p1-94.el6 will be installed
--> Processing Dependency: openssh = 5.3p1-94.el6 for package:
openssh-server-5.3p1-94.el6.x86_64
--> Processing Dependency: libcrypto.so.10(libcrypto.so.10)(64bit) for package:
openssh-server-5.3p1-94.el6.x86_64
--> Processing Dependency: libcrypto.so.10(OPENSSL_1.0.1)(64bit) for package:
openssh-server-5.3p1-94.el6.x86_64
--> Processing Dependency: libwrap.so.0()(64bit) for package:
openssh-server-5.3p1-94.el6.x86_64
--> Processing Dependency: libfipscheck.so.1()(64bit) for package:
openssh-server-5.3p1-94.el6.x86_64
--> Running transaction check
---> Package fipscheck-lib.x86_64 0:1.2.0-7.el6 will be installed
--> Processing Dependency: /usr/bin/fipscheck for package:
fipscheck-lib-1.2.0-7.el6.x86_64
---> Package openssh.x86_64 0:5.3p1-94.el6 will be installed
---> Package openssl.x86_64 0:1.0.0-27.el6_4.2 will be updated
---> Package openssl.x86_64 0:1.0.1e-16.el6_5.7 will be an update
--> Processing Dependency: make for package: openssl-1.0.1e-16.el6_5.7.x86_64
---> Package tcp_wrappers-libs.x86_64 0:7.6-57.el6 will be installed
--> Running transaction check
---> Package fipscheck.x86_64 0:1.2.0-7.el6 will be installed
---> Package make.x86_64 1:3.81-20.el6 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
openssh-server x86_64 5.3p1-94.el6 base 311 k
Installing for dependencies:
fipscheck x86_64 1.2.0-7.el6 base 14 k
fipscheck-lib x86_64 1.2.0-7.el6 base 8.3 k
make x86_64 1:3.81-20.el6 base 389 k
openssh x86_64 5.3p1-94.el6 base 258 k
tcp_wrappers-libs x86_64 7.6-57.el6 base 62 k
Updating for dependencies:
openssl x86_64 1.0.1e-16.el6_5.7 updates 1.5 M
Transaction Summary
================================================================================
Install 6 Package(s)
Upgrade 1 Package(s)
Total download size: 2.5 M
Downloading Packages:
--------------------------------------------------------------------------------
Total 569 kB/s | 2.5 MB 00:04
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID c105b9de:
NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
Importing GPG key 0xC105B9DE:
Userid : CentOS-6 Key (CentOS 6 Official Signing Key)
<centos-6-key(a)centos.org>
Package: centos-release-6-4.el6.centos.10.x86_64 (@febootstrap/$releasever)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : tcp_wrappers-libs-7.6-57.el6.x86_64 1/8
Installing : 1:make-3.81-20.el6.x86_64 2/8
Updating : openssl-1.0.1e-16.el6_5.7.x86_64 3/8
Installing : fipscheck-lib-1.2.0-7.el6.x86_64 4/8
Installing : fipscheck-1.2.0-7.el6.x86_64 5/8
Installing : openssh-5.3p1-94.el6.x86_64 6/8
Installing : openssh-server-5.3p1-94.el6.x86_64 7/8
groupadd: failure while writing changes to /etc/group
Cleanup : openssl-1.0.0-27.el6_4.2.x86_64 8/8
Verifying : 1:make-3.81-20.el6.x86_64 1/8
Verifying : tcp_wrappers-libs-7.6-57.el6.x86_64 2/8
Verifying : fipscheck-1.2.0-7.el6.x86_64 3/8
Verifying : openssl-1.0.1e-16.el6_5.7.x86_64 4/8
Verifying : openssh-5.3p1-94.el6.x86_64 5/8
Verifying : openssh-server-5.3p1-94.el6.x86_64 6/8
Verifying : fipscheck-lib-1.2.0-7.el6.x86_64 7/8
Verifying : openssl-1.0.0-27.el6_4.2.x86_64 8/8
Installed:
openssh-server.x86_64 0:5.3p1-94.el6
Dependency Installed:
fipscheck.x86_64 0:1.2.0-7.el6 fipscheck-lib.x86_64 0:1.2.0-7.el6
make.x86_64 1:3.81-20.el6 openssh.x86_64 0:5.3p1-94.el6
tcp_wrappers-libs.x86_64 0:7.6-57.el6
Dependency Updated:
openssl.x86_64 0:1.0.1e-16.el6_5.7
Complete!
---> e869dfd88b15
Removing intermediate container 65f28c081323
Step 2 : RUN sed -i 's/#PermitEmptyPasswords no/PermitEmptyPasswords
yes/;s/#UseDNS yes/UseDNS no/' /etc/ssh/sshd_config
---> Running in 8673e7861c41
sed: warning: failed to set default file creation context to
system_u:object_r:file_t:s0: Read-only file system ---> f49ebe0bc026
Removing intermediate container 8673e7861c41
Step 3 : CMD service sshd start ; bash
---> Running in b4db6af6261e
---> b9d7e3852943
Removing intermediate container b4db6af6261e
Successfully built b9d7e3852943
Expected results:
A build and run with no errors.
Everything works as expected when run for instance in a boot2docker vm:
https://github.com/boot2docker/boot2docker/releases/download/v0.9.1/boot2...
Additional info:
$ getenforce
Permissive
The error is recent. I am not sure if the problem is Docker, selinux, or Centos
base files, but the full operation used to succed without any problem in past.
Note sed warning:
sed: warning: failed to set default file creation context to
system_u:object_r:file_t:s0: Read-only file system ---> f49ebe0bc026
When running a container from that image, the ssh fails:
$ docker run -t -i sshd
Generating SSH1 RSA host key: No such file or directory
[ OK ]
Generating SSH2 RSA host key: No such file or directory
[ OK ]
Generating SSH2 DSA host key: No such file or directory
[ OK ]
Starting sshd: Privilege separation user sshd does not exist
[FAILED]
bash-4.1# exit
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months
[Bug 1096849] New: docker daemon for epel7 doesn't allow for additional options
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1096849
Bug ID: 1096849
Summary: docker daemon for epel7 doesn't allow for additional
options
Product: Fedora EPEL
Version: epel7
Component: docker-io
Severity: medium
Assignee: lsm5(a)redhat.com
Reporter: jperrin(a)centos.org
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
For el6, epel's docker build creates /etc/sysconfig/docker, which allows other
options to be passed to the docker daemon. the systemd unit files for epel7's
docker build do not.
Version-Release number of selected component (if applicable):
docker-io-0.10.0-2.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. yum install docker-io
2. less /usr/lib/systemd/system/docker.service
Actual results:
There is no $other_args defined in the systemd unit file, nor is there an
/etc/sysconfig/docker in which to define the options.
Expected results:
Same as the el6 docker. You should be able to pass additional arguments for
bridging, dns, or restart options
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months
[Bug 1084232] New: Docker fails to pull images from behind a proxy server
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1084232
Bug ID: 1084232
Summary: Docker fails to pull images from behind a proxy server
Product: Fedora
Version: 20
Component: docker-io
Severity: low
Assignee: lsm5(a)redhat.com
Reporter: dbond(a)nrggos.com.au
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, skottler(a)redhat.com,
vbatts(a)redhat.com
Description of problem: Docker-io does not work behind a proxy server
The docker daemon does not use the proxy and attempts to access directly
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
HTTP_PROXY=http://my_proxy:3128/ docker pull busybox
Actual results:
Pulling repository busybox
2014/04/04 08:56:42 Get https://index.docker.io/v1/repositories/busybox/images:
dial tcp: lookup index.docker.io on [10.x.x.x]:53: no such host
Expected results:
Unable to find image 'busybox' locally
Pulling repository busybox
769b9341d937: Download complete
511136ea3c5a: Download complete
bf747efa0e2f: Download complete
48e5f45168b9: Download complete
hello world
Additional info:
Fixed by adding an environment file to docker.service
Add file /etc/sysconfig/docker containing
HTTP_PROXY=http://my_proxy:3128
Add
EnvironmentFile=-/etc/sysconfig/docker
to docker.service file
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months
[Bug 1088125] New: docker top stopped working, cgroup path changed
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1088125
Bug ID: 1088125
Summary: docker top stopped working, cgroup path changed
Product: Fedora
Version: 20
Component: docker-io
Severity: high
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, skottler(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
The `docker top` command stopped working, the path to cgroup processes had
changed.
Version-Release number of selected component (if applicable):
docker-io-0.10.0-2.fc20.x86_64
How reproducible:
always
Steps to Reproduce:
1. docker run -i fedora bash
2. docker top $NAME
Actual results:
[root@t530 ~]# docker top determined_jones
2014/04/16 07:47:52 Error: open
/sys/fs/cgroup/devices/system.slice/docker/93dfbd4d375cf026df215d87b5d93de8b0a9bd55094e33c2ca3322cd6afb53f1/tasks:
no such file or directory
Expected results:
list of processes...
Additional info:
[root@t530 ~]# ls /sys/fs/cgroup/devices/system.slice/
cgroup.clone_children
cgroup.event_control
cgroup.procs
devices.allow
devices.deny
devices.list
docker-93dfbd4d375cf026df215d87b5d93de8b0a9bd55094e33c2ca3322cd6afb53f1.scope
notify_on_release
tasks
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months