Closed mplsgrant closed 2 months ago
@mplsgrant thank you for creating this bug, you are right if the OS does NOT support 9p it will not work, which I dont know what we could do about it, btw do you mind sharing which cloud did you try the debian 6 on ? and what is the Exact version that they stopped including 9p ?
but the lease we could do is Detect that the OS does NOT support 9p and Exit Nicely with a more user friendly way
@mplsgrant would you be interested to make a PR for this?
do you mind sharing which cloud did you try the debian 6 on ?
I used cloud.google.com. Here's more info from uname -a
:
Linux ... 6.1.0-20-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 GNU/Linux
and what is the Exact version that they stopped including 9p
I'm not sure, but this bug report gives me the impression that 9p has not existed in the debian cloud kernel since at least the year 2020.
would you be interested to make a PR for this?
While I am very tempted to contribute in this way, I do not have code to share that would help solve this issue. Also, I do not have the bandwidth at the moment to investigate and write the code.
Redhat also hates 9p, which lead to docker-machine to not support the mount feature in the "kvm" driver:
At the time they were hoping for vsock, which never happened. And now it is virtiofs, being rewritten in Rust...
I think that reverse-sshfs (as in sshocker
) is the most compatible mount solution.
I can try and take a stab at this (graceful exit) - assuming there is no rush. /assign
@xcarolan first come first serve :) go ahead
So i've added a very minor change to this, (first change) basically exiting gracefully..
I'm not exactly thrilled with the outcome, I would have liked to check the host system first for support of 9p so I could provide a more specific error (but I didn't see a way of doing this). Any thoughts?
shouldn't this be closed?
What Happened?
Context
uname -a
: Linux ... 6.1.0-20-cloud-amd64Issue
minikube mount /path/on/host:/path/on/vm
gives the following error:Cause
I believe the debian cloud image does not (and will not) include 9p:
The
mount
command does work with ubuntu. Here's the view from ubuntu and from debian which shows the different kernels in use.Attach the log file
log file
Log file created at: 2024/04/22 14:36:43 Running on machine: machine-ready-20240420-020624 Binary: Built with gc go1.22.1 for linux/amd64 Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg I0422 14:36:43.016777 5138 out.go:291] Setting OutFile to fd 1 ... I0422 14:36:43.016948 5138 out.go:343] isatty.IsTerminal(1) = false I0422 14:36:43.016954 5138 out.go:304] Setting ErrFile to fd 2... I0422 14:36:43.016961 5138 out.go:343] isatty.IsTerminal(2) = false I0422 14:36:43.017277 5138 root.go:338] Updating PATH: /home/USER/.minikube/bin W0422 14:36:43.017426 5138 root.go:314] Error reading config file at /home/USER/.minikube/config/config.json: open /home/USER/.minikube/config/config.json: no such file or directory I0422 14:36:43.017621 5138 mustload.go:65] Loading cluster: minikube I0422 14:36:43.018109 5138 config.go:182] Loaded profile config "minikube": Driver=docker, ContainerRuntime=docker, KubernetesVersion=v1.30.0 I0422 14:36:43.019037 5138 cli_runner.go:164] Run: docker container inspect minikube --format={{.State.Status}} I0422 14:36:43.042359 5138 host.go:66] Checking if "minikube" exists ... I0422 14:36:43.042738 5138 cli_runner.go:164] Run: docker system info --format "{{json .}}" I0422 14:36:43.153818 5138 info.go:266] docker info: {ID:7fe2a9e9-e2e1-4517-b90f-5bc4edddc88e Containers:5 ContainersRunning:1 ContainersPaused:0 ContainersStopped:4 Images:7 Driver:overlay2 DriverStatus:[[Backing Filesystem extfs] [Supports d_type true] [Using metacopy false] [Native Overlay Diff true] [userxattr false]] SystemStatus:Operating System
Other
Driver
Docker