Conversation
vendor.conf
Outdated
There was a problem hiding this comment.
Is a cherry-pick opened for the patch to get it into the 1.2 branch in containerd?
There was a problem hiding this comment.
@dmcgowan Not sure how you're cutting 1.2, or just refreshing from master on each release?
There was a problem hiding this comment.
Oh, nevermind, I see that the 1.2-beta's are still tagged from master, and that there's no 1.2 branch yet
|
Oops, looks like there's an issue with vendoring; |
913e9bf to
13705bf
Compare
|
Yeah, looks like containerd is pulling in new bits of continuity. Did a revendor on containerd/continuity without bumping the commit. Hopefully should work this time. |
13705bf to
c5f2b83
Compare
|
Nope, have had to bump containerd/continuity as well - now at f44b615e492bdfb371aae2f76ec694d9da1db537. Third time lucky.... |
Signed-off-by: John Howard <[email protected]>
c5f2b83 to
e57b2a8
Compare
|
And also bumped go-runc to 5a6d9f37cfa36b15efba46dc7ea349fa9b7143c3 to match containerd/containerd to avoid compilation error |
|
Vendor passes now 😺 |
Codecov Report
@@ Coverage Diff @@
## master #37877 +/- ##
=========================================
Coverage ? 36.11%
=========================================
Files ? 610
Lines ? 45083
Branches ? 0
=========================================
Hits ? 16281
Misses ? 26563
Partials ? 2239 |
|
@dmcgowan @crosbymichael You guys OK with this? I should get this in first before revendoring moby/buildkit which already has the PR merged to bump its version of containerd and move to bbolt. Thx. |
|
LGTM |
Signed-off-by: John Howard [email protected]
This bumps containerd to d97a907f7f781c0ab8340877d8e6b53cc7f1c2f6. This is specifically to pick up this fix containerd/containerd#2634 removing boltdb which has a bug on Windows, and moving to bbolt, the maintained fork with the fix instead.
This PR directly relates to #37843 where there's a large dependency chain involved here to get all related components moved to bbolt. @thaJeztah @dmcgowan PTAL.
Note - there isn't a tagged release of v1.2 yet containing this fix, hence using the latest commit ID on master as at the time of writing.