Change:
I am trying to bring up a kind cluster with containerd in order to run e2e test on mac + kind. Not sure whether this is a bug or I missed some prerequisites. Any help would be greatly appreciated :) building the image dra/node:latest works as expected:bringing up the kind cluster failed (seems that kubelet is unhealthy and healthchecked failed) below the control plane logs: below the logs of one worker: successfully bring up the kind cluster with containerd Tried on M2 macbook pro I followed NONE Darwin MacBook-Pro-de- 22.1.0 Darwin Kernel Version 22.1.0: Sun Oct 9 20:19:12 PDT 2022; root:xnu-8792.41.9~3/RELEASEARM64T6020 arm64 arm Darwin No response No response
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
what type of mac you're using? for m1/m2 mac, you need to replace the linux-amd64 with linux-arm64(your log seems like using m1/m2 mac which same as the problem I've met before)
thanks I am going to try that
ping me if you can run e2e on mac. I setup the cluster but failed to run the e2e test..
can you please share the exact command you tried and the failure ?
If you use a newer version of kind you might not need to clobber the included containerd, not sure what version is required And yes, on M1/M2 you need to use arm binaries/images.
this is the command that I tried !
It worked for me just fine on M2 machine with this obvious fix for the build script: Here is a test output:
I'll submit a PR with the fix. Updating the documentation would be also nice to have. I hope and can do that.
DRA tests fail on kind 0.18.0. Which Containerd version is used there?
It was the latest 1.6.x at release time. 1.6 is their LTS branch before 2.0 comes which has some tricky changes for us to deal with (notably the CRI hosts config deprecation which will break all our local registry users :/)
Unfortunately 1.6 doesn't have CDI support, which DRA depends on. The version used in the build script is 1.6.0-830-g34d078e99, but it was probably built from containerd master after 1.6 was released.
thanks for providing the details. you could run the e2e as shown by and find the result

Discussion:
} trap cleanup EXIT <ins> goarch=$(go env GOARCH) </ins> kind build node-image --image "$tag" "$(pwd)" <del> curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/$containerd-linux-amd64.tar.gz | tar -C "$tmpdir" -vzxf - curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/runc.amd64 >"$tmpdir/runc" </del> <ins> curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/$containerd-linux-"$goarch".tar.gz | tar -C "$tmpdir" -vzxf - curl -L --silent https://github.com/kind-ci/containerd-nightlies/releases/download/$containerd/runc."$goarch" >"$tmpdir/runc" </ins> cat >"$tmpdir/Dockerfile" <<EOF FROM $tag