Public bug reported:

(please refer to
https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
context)

Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

Steps to reproduce:
- Install latest Docker
- Run 300 containers with health check (for i in {1..300}; do docker run -d -it 
--restart=always --name poc_$i talves/health_poc; done)
- Send termination signal to the containers (docker kill -s TERM $(docker ps -q)
- A few processes are going to be stuck in "uninterruptible sleep" ("D" state). 
The only know way to recover from this is host reboot

Expected behavior:
- All containers should be terminated without any dangling process

Actual behavior:
- Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

A fix is provided on kernel 4.12 - it would be nice if it could be
backported and included in the next Ubuntu release within the supported
kernel.

Thanks in advance

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1698264

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  New

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698264/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to