bug: Failed to run k3s (with containerd) on Intel VM with Apple M1

[gaocegege]

Describe the bug

I created a linux intel VM on my M1 macOS and a k3s cluster there.

K3s uses containerd to create containers. All the containers show: seccomp is not supported.

multipass does not have such issue. I could create the k3s cluster in multipass VM successfully.

To Reproduce

$ curl -sfL https://get.k3s.io | sh -
$ sudo k3s kubectl describe pods --all-namespaces

Expected behavior

$ sudo k3s kubectl get pods --all-namespaces

All the pods should be running, instead of ContainerCreating

Logs

I do not think it is related.

Screenshots and additional context (optional)

No response

[kdrag0n]

It may not be feasible to support running full-blown k3s under Rosetta emulation. I'm not familiar with Kubernetes, but consider doing it like Docker multi-platform if possible: x86 containers on an arm64 host.

[gaocegege]

But multipass works well.

I am not sure if it is related to kubernetes. I think it is only about containerd. Because the kubernetes does not raise any error. The container runtime (containerd) returns seccomp not supported.

[kdrag0n]

Multipass emulates a full x86 VM, which is better for compatibility but extremely slow. OrbStack uses Rosetta emulation instead. I'll take a look but unfortunately this may very well turn out to be infeasible/wontfix.

[gaocegege]

Gotcha, thanks!

[mihirsamdarshi]

Hi, do you think it would be feasible to support x86-emulated Kubernetes on Apple Silicon through OrbStack?

[kdrag0n]

Very unlikely.

[addozhang]

Have the same issue. After research, I got a workaround solution by specify k3s (with k3s installation option --docker) to use a x86 Docker container runtime.

The detail solution is here.