Docker won't be restarted once containerd is killed
Bug #1835523 reported by
Balint Reczey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| containerd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
From upstream bug https:/
After containerd is temporarily killed and restarted, docker should continue working.
Containerd should also be patched to be killed less often and restart.
| tags: | added: id-5ce59fdf336b725d9e95173c |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in containerd (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package containerd - 1.2.7-0ubuntu2
---------------
containerd (1.2.7-0ubuntu2) eoan; urgency=medium
[ Łukasz 'sil2100' Zemczak ]
* Add Restart=always and RestartSec=2 to the containerd service.
Also set the containerd OOM adjustment level to -999 (LP: #1835523)
-- Balint Reczey <email address hidden> Fri, 05 Jul 2019 13:13:39 +0200