Fix build against new runc version
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
golang-github-containers-buildah (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
libpod (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
runc/1.
proposed) but libpod and golang-
Both packages, libpod and golang-
[Test Plan]
Make sure libpod and golang-
[Where problems could occur]
The patches which will be enabled are well tested by Debian (they are not commented out there because they already have a newer runc), but if a problem could occur it would be where the patches are applied which is the implementation of how devices and permissions are managed in a linux system. Check the patches for more info.
Changed in golang-github-containers-buildah (Ubuntu): | |
status: | New → Fix Released |
Changed in libpod (Ubuntu): | |
status: | New → Fix Released |
Changed in golang-github-containers-buildah (Ubuntu Groovy): | |
status: | New → In Progress |
Changed in libpod (Ubuntu Groovy): | |
status: | New → In Progress |
Thanks, Lucas.
I was involved in the investigation of the libpod breakage and feel confident that this is the right way to go.
I did try to build both libpod and buildah with equivalent patches locally, and everything succeeds. I'm +1 on both patches.