k3s - container runtime configuration

[rokf]

Hello,

There's a project that is using this plugin that I'd like to get running on an Ubuntu VM (amd64) running on MacOS with an M-series chip (M1). This are the instructions for the project - https://github.com/FIWARE/data-space-connector/blob/main/doc/deployment-integration/local-deployment/LOCAL.MD.

I'm dealing with the following issue with the k3s Docker image that is used by this plugin out of the box:

Failed to create pod sandbox: rpc error: code = Unknown desc = failed to generate sandbox container spec options: failed to generate seccomp spec opts: seccomp is not supported

I found a blog post that suggests that this issue can be mitigated by passing the --docker flag to k3s, which will choose a different container runtime - https://addozhang.medium.com/set-up-an-x86-k3s-cluster-on-apple-silicon-with-orbstack-9ea4e6f84461.

The --docker flag is experimental - https://docs.k3s.io/cli/agent#experimental.

If I understand correctly, k3s-maven-plugin's k3s:run goal will run the rancher/k3s container, which runs k3s agent - https://docs.k3s.io/cli/agent.

I'd therefore like to try and pass some flags to the agent. According to https://git.kokuwa.io/kokuwaio/k3s-maven-plugin/src/branch/main/docs/goal/run.md there's no configuration property that'd allow me to do that, except if I make a custom Docker image (i.e. "fork" rancher/k3s) and pass the flags by overriding the default CMD, correct? Then I'd have to pass the custom image in to the imageRepository property of the run goal, which would then run the k3s agent with my customisations (flags) applied.

If so, would it make sense to add additional properties for the run goal which would allow customisations without the need to change the container image?

Image layers of the current (time of writing) rancher/k3s:latest image can be found at https://hub.docker.com/layers/rancher/k3s/latest/images/sha256-2ce62972e2b3ef113d7e4fac5aef10169048fae1a5f73e1d2483586defceea5a.

Thank you!