You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all scripts are pointing to a hard-coded digest for the amd64 image. With the advent of MacOS M1 and M2, we can likely fall back to just specifying the tagged images which now include both archs, see: https://hub.docker.com/r/kindest/node/tags
Though, it does seem like we cannot run KinD with amd64 natively on the arm64 architecture...
Though, it does seem like we cannot run KinD with amd64 natively on the arm64 architecture...
Correct, at least not without a VM, the way docker does cross-architecture containers is only suitable for simple applications, it cannot really do anything complex interacting with the kernel because it doesn't emulate syscalls, only userspace.
Currently, all scripts are pointing to a hard-coded digest for the amd64 image. With the advent of MacOS M1 and M2, we can likely fall back to just specifying the tagged images which now include both archs, see: https://hub.docker.com/r/kindest/node/tags
Though, it does seem like we cannot run KinD with amd64 natively on the arm64 architecture...
kubernetes-sigs/kind#2972
kubernetes-sigs/kind#2718
The text was updated successfully, but these errors were encountered: