[SRU] Update to containerd 1.3.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
containerd (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bionic |
Fix Released
|
High
|
Unassigned | ||
Disco |
Invalid
|
High
|
Unassigned | ||
Eoan |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
Docker.io is a fast moving project, and SRU policy for containerd is that getting its .1 update out to LTS users quickly will bring more benefit than risks. This policy was approved by the tech board as of 2016-09-20.
[Test Case]
Checking autopkgtest is sufficient. See https:/
[Regression Potential]
See https:/
[Fix]
1.3.1 is currently in focal-proposed. Any block-proposed tag should be removed to enable it to pass and land, then once migrated can be uploaded for SRU to requested series.
[Original Report]
Hey folks, we've got a Charmed Kubernetes bug[1] that requires us to run containerd 1.3.0+ to fix. Can we get the apt package in bionic universe updated to 1.3.1 or at least 1.3.0?
If possible, we would like to test the updated containerd package in bionic-proposed before it is released.
[1]: https:/
description: | updated |
Hello,
can you elaborate a bit more on what bug the update to 1.3.0 is fixing? It's usually better to cherry pick the exact fix needed instead of doing a somewhat big upgrade like this. Also, the 1.3.x series isn't even in ubuntu focal yet (1.3.1 is in focal-proposed).