Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

I am able to start processes in unprivileged container via runuser (but see bug 1120567 about it being broken in docker 1+). However, I do not seem to be able to kill the process from my root shell anymore.

Version-Release number of selected component (if applicable):

docker-0.11.1-22.el7.x86_64

How reproducible:

Deterministic.

Steps to Reproduce:
1. Run # docker run -ti rhel7 /bin/bash
2. In the container install /usr/bin/ps: bash-4.2# yum install -y /usr/bin/ps
3. In the container, run process as different user: bash-4.2# runuser -u ftp sleep 6000 &
4. Get the pid of the sleep process: bash-4.2# ps au | grep sleep
root        33  0.0  0.0  41360  1440 ?        S    04:28   0:00 runuser -u ftp sleep 6000
ftp         34  0.0  0.0   4312   360 ?        S    04:28   0:00 sleep 6000
root        46  0.0  0.0   9032   672 ?        S+   04:29   0:00 grep sleep
5. Attempt to kill the process: bash-4.2# kill 34 ; echo $?

Actual results:

bash: kill: (34) - Operation not permitted
1

Expected results:

0

and process killed.

Additional info:

I can send the signal to the process via runuser: runuser -u ftp kill 34

With docker-1.1.1 I get a different error, basically runuser is failing,

It works if I execute:

docker run --cap-add audit_write --rm -ti fedora /bin/sh

And in this case I don't see a problem with killing the process.

pscap shows the following access.

20785 6386  root        sh                chown, dac_override, fowner, fsetid, kill, setgid, setuid, setpcap, net_bind_service, net_raw, sys_chroot, mknod, audit_write, setfcap, cap_37

I just ran this test with

docker-1.1.1-3.el7.x86_64

And it worked fine.

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.

http://rhn.redhat.com/errata/RHBA-2014-1266.html