Minikube on WSL causes Exec Format Error

[Sefi4]

What Happened?

Opening VS code on WSL running code works fine.
Then run: minikube start
Afterward, try to open VS code again using: code causes:
/mnt/c/Users/<username>/AppData/Local/Programs/Microsoft VS Code/bin/code: 61: /mnt/c/Users/<username>/AppData/Local/Programs/Microsoft VS Code/Code.exe: Exec format error

I think that's the same issue as:
#17700
but I'm still experiencing it (there wasn't a release yet)?

I'm using minikube v1.32.0 on WSL Ubuntu 22.04 (amd64) with docker desktop v4.28.0

Attach the log file

logs.txt

Operating System

Ubuntu

Driver

Docker

[afbjorklund]

Sounds like the same

[Sefi4]

@afbjorklund agree, it's the same.
However, the linked issue is closed and the issue persists.
I guess the fix is merged?

[afbjorklund]

You can try the newer images, to see if it fixes the issue (or list binfmt misc, to verify it's the same)

But it seems you are trying to run Windows binaries in Linux, with wine or whatever

[martin-jeremic]

Got same issue with Ubuntu 20.04.4 LTS, minikube v1.32.0 and Docker version 25.0.3, build 4debf41

[medyagh]

@Sefi4 can you plz try minikube 1.33.0beta we merged a PR that apparantly fixed an issue with binfmt

plz go here and select Beta and choose your OS
https://minikube.sigs.k8s.io/docs/start/

[Sefi4]

Thanks for the suggestion @medyagh

Unfraternally it didn't help :(

minikube start
😄 minikube v1.33.0-beta.0 on Ubuntu 22.04 (amd64)
🆕 Kubernetes 1.29.3 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.29.3
✨ Using the docker driver based on existing profile
👍 Starting "minikube" primary control-plane node in "minikube" cluster
🚜 Pulling base image v0.0.43-beta.0 ...
🔄 Restarting existing docker container for "minikube" ...
❗ Image was not built for the current minikube version. To resolve this you can delete and recreate your minikube cluster using the latest images. Expected minikube version: v1.32.0 -> Actual minikube version: v1.33.0-beta.0
🐳 Preparing Kubernetes v1.28.3 on Docker 24.0.7 .../ Bad local forwarding specification '0:localhost:8443'

🔗 Configuring bridge CNI (Container Networking Interface) ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟 Enabled addons: storage-provisioner, default-storageclass
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

code
/mnt/c/Users/<user>/AppData/Local/Programs/Microsoft VS Code/bin/code: 61: /mnt/c/Users/<user>/AppData/Local/Programs/Microsoft VS Code/Code.exe: Exec format error

[afbjorklund]

Any previously existing rules would need to be restored, either manually or through rebooting (the Linux)

[liweizhi]

I am working a dev container (Docker Desktop +WSL), once I run minikube start (from WSL, or even from the dev container), the docker credential helper will be broken on WSL. The error is similar with this issue:

docker logout
Removing login credentials for https://index.docker.io/v1/
WARNING: could not erase credentials:
https://index.docker.io/v1/: error erasing credentials - err: fork/exec /usr/bin/docker-credential-desktop.exe: exec format error, out: ``

Restart WSL can fix it until I start minikube

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.