Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1186066 - The docker stop operation doesn't work with --pid=host containers containing multiple processes
The docker stop operation doesn't work with --pid=host containers containing ...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker (Show other bugs)
7.2
x86_64 Linux
urgent Severity high
: rc
: ---
Assigned To: Daniel Walsh
atomic-bugs@redhat.com
: Extras
Depends On:
Blocks: 1186007
  Show dependency treegraph
 
Reported: 2015-01-26 18:46 EST by Steven Dake
Modified: 2016-05-12 11:15 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-12 11:15:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1034 normal SHIPPED_LIVE Moderate: docker security, bug fix, and enhancement update 2016-05-12 15:15:01 EDT

  None (edit)
Description Steven Dake 2015-01-26 18:46:45 EST
Description of problem:
docker stop blocks and fails to stop all processes in the container.

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

How reproducible:
100%

Steps to Reproduce:
Make sure libvirtd, nova-compute, nova-network, and virtlockd is not running on the host.  If they are, disable them and reboot.

1. git clone https://github.com/sdake/compute-upgrade.git
2. cd compute-upgrade/tools
3. ./start-compute
4. Use docker ps to obtain docker container id for the nova-compute container
5. use docker stop <CONTAINER_ID> where container id is the container id from step #4

Actual results:
The operation blocks
killall -9 libvirtd
killall -9 virtlockd

This will unblock the docker stop operation

Expected results:
docker stop operation should terminate the libvirtd and virtlockd process and return within a few seconds.

Additional info:
Comment 1 Steven Dake 2015-01-26 18:48:57 EST
Upstream issue tracker:

https://github.com/docker/docker/issues/10303
Comment 2 Steven Dake 2015-01-26 18:50:20 EST
Cherry-pick of upstream patch that has been verified to resolve the problem:

https://github.com/rhatdan/docker/commit/0b4cade8b81cf8980977b5d353d7e6a0c08838b7
Comment 4 Daniel Walsh 2015-01-27 09:48:44 EST
We have a build ready to go with this fix, but need the goahead on building a new package.
Comment 5 Daniel Walsh 2015-01-30 14:28:55 EST
Fixed in 
docker-1.4.1-37.el7.x86_64.rpm
Comment 8 Steven Dake 2015-02-07 08:46:54 EST
Daniel,

Any chance you could backport the latest rhel docker to fedora 21?  There is no --pid=host feature which would be nice for testing OpenStack upgrades.

Regards
-steve
Comment 9 Daniel Walsh 2015-02-09 05:25:18 EST
That fix should be in docker-1.5 which I believe will be released tomorrow by docker. As soon as we get a released version we will update fedora 21 and Rawhide.  Will probably update f20 also.
Comment 11 Luwen Su 2016-05-01 04:10:59 EDT
This should work fine in docker-1.9.1-38.el7.x86_64, move to verified

# docker ps
CONTAINER ID        IMAGE                           COMMAND             CREATED             STATUS              PORTS               NAMES
de946711322b        sdake/fedora-rdo-nova-compute   "/start.sh"         32 seconds ago      Up 14 seconds                           cocky_lichterman
0f60869bd76e        sdake/fedora-rdo-nova-libvirt   "/start.sh"         45 seconds ago      Up 32 seconds                           focused_swirles
10d36abd5fa2        sdake/fedora-rdo-nova-network   "/start.sh"         49 seconds ago      Up 45 seconds                           berserk_wescoff
[root@dhcp-0-137 ~]# docker stop de946711322b
de946711322b
Comment 13 errata-xmlrpc 2016-05-12 11:15:50 EDT
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.

https://rhn.redhat.com/errata/RHSA-2016-1034.html

Note You need to log in before you can comment on or make changes to this bug.