Bug 1302814

Summary: regression: Unattached child process should exist when the container is killed in docker container with pid=host
Product: Red Hat Enterprise Linux 7 Reporter: Daniel Walsh <dwalsh>
Component: dockerAssignee: Mrunal Patel <mpatel>
Status: CLOSED NOTABUG QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: adimania, admiller, amurdaca, andreas.bierfert, dustymabe, dwalsh, extras-qa, ichavero, jcajka, jchaloup, lsm5, marianne, miminar, mpatel, steven.dake, vbatts, zhang.lei.fly
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1302807 Environment:
Last Closed: 2016-02-22 19:37:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1302807    
Bug Blocks:    

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.