Docker containers lose their cgroup after systemd reload
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
docker.io (Ubuntu) |
Fix Released
|
Undecided
|
Martin Pitt | ||
systemd (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
After a Systemd reload & any service restart, docker top no longer show process of containers:
To reproduce this issue, do the following step:
# docker run -d --name test busybox sleep 1d
# docker top test
UID PID PPID C STIME TTY TIME CMD
root 26416 1072 1 18:05 ? 00:00:00 sleep 1d
# systemctl --system daemon-reload && systemctl restart atd.service
# docker top test
UID PID PPID C STIME TTY TIME CMD
[ no process listed... but sleep is still running]
Note: this idea of restarting any service restart come from patch https:/
After few searching, this seems to be due to process from the container being moved in other cgroup by Systemd. More details on https:/
Depending on version of Systemd (Wily or Xenial), this issue:
* Wily: Happend with Docker 1.10 (with default option)
* Wily: Does NOT happend with Docker 1.10 and --exec-opt native.
* Wily: Does NOT happend with Docker 1.9
* Xenial: Does always happend (Docker 1.9, 1.10 with or without native.
I don't know if this issue is a Systemd issue, a Docker issue... or in middle.
Changed in docker.io (Ubuntu): | |
status: | In Progress → Fix Committed |
assignee: | nobody → Martin Pitt (pitti) |
Status changed to 'Confirmed' because the bug affects multiple users.