Bug 1302814 - regression: Unattached child process should exist when the container is killed in docker container with pid=host
Summary: regression: Unattached child process should exist when the container is kille...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Mrunal Patel
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On: 1302807
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-28 16:54 UTC by Daniel Walsh
Modified: 2019-03-06 01:06 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1302807
Environment:
Last Closed: 2016-02-22 19:37:28 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Daniel Walsh 2016-01-28 16:54:29 UTC 
+++ This bug was initially created as a clone of Bug #1302807 +++

Description of problem:

In the docker container with pid=host, the unattached child process shouldn't be killed when killing the container. 

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

docker 1.9.1
centos 7

How reproducible:


Steps to Reproduce:
1. start a container with pid=host and command libvirtd
2. launch a qemu process using virsh in the container. The start qemu process will be unattached.
3. try to kill the container using `docker kill -s KILL <container_id>

Actual results:

the qemu process is killed, too.

Expected results:

the unattached qemu process is not killed.


Additional info:
Comment 2 Daniel Walsh 2016-02-22 19:37:28 UTC 
Turns out this is a bug in the testing environment.
Note You need to log in before you can comment on or make changes to this bug.