Bug: Healthcheck failed on running k3s preset example

[jukomericki]

Describe the bug
I wanted to try and use the k3s preset as it seemeed very developer friendy, but on running the preset_test.go a healthcheck failed is repeatedly logged, more precisely kubeconfig cannot be found

To Reproduce
To reproduce clone the repo and go test preset_test.go in preset/k3s

Expected behavior
An expected behaviour would be to fetch the kube config succesfullyy

Screenshots

System:

• OS: MacOS
• Version 12.3.1
• Docker desktop version 4.4.2 (engine version 20.10.12)

[orlangure]

Hi @jukomericki, sorry to hear that you had issues with k3s preset😿

Do you use MacOS on arm64 architecture? I think the issue might be caused by poor performance of amd64 docker images on arm64 systems. I'll have to rebuild k3s preset images for both architectures (if possible). I'll try to work on this next weekend.

[jukomericki]

@orlangure I have amd64 arch.
Thank you I'll be the first one to try the rebuilt presets 😄

[orlangure]

Hi @jukomericki,

Since you have amd64 macos, using rebuilt images won't help. Anyway, I tried building the images for arm64 architecture (I use it...) and it appears that k3s-in-docker doesn't work at all on arm64.

Would you mind adding the following options to your code?

gnomock.WithDebugMode(),
gnomock.WithLogWriter(os.Stdout),

Please share the complete logs after you try this out. We might see something useful from internal container logs. Note that k3s might take a couple minutes to start.