Build succeeded.

• containerd-build-arm64 : SUCCESS in 7m 40s (non-voting)

Codecov Report

Merging #4088 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4088   +/-   ##
=======================================
  Coverage   42.53%   42.53%           
=======================================
  Files         130      130           
  Lines       14828    14828           
=======================================
  Hits         6307     6307           
  Misses       7602     7602           
  Partials      919      919

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3868dd7...ddae905. Read the comment docs.

LGTM

nit: can you squash commits?

Build succeeded.

• containerd-build-arm64 : SUCCESS in 8m 05s (non-voting)

Hi @mxpv,

Do you happen to know when the next ContainerD release will occur? I noticed the most recent one is only 23 days ago, but the Kubernetes machine images built from image-builder are having race bugs due to the start order of cloud-init and containerd. We put all of the right Wants/After/etc. statements in place, but it turns out that the race still occurs (kubernetes-sigs/image-builder#173) because of the lack of sd_notify in containerd. Since this issue was fixed in this PR, we could really use a new version of ContainerD with the patch. Thanks!