Minikube ssh failure after running minikube mount.

[angelosanramon]

What Happened?

After running minikube mount, minikube ssh no longer works. Minikube version: v1.35.0.

mounted a volume:

❯ minikube mount ~/workspace/tmp/keycloak_certs:/home/docker
📁  Mounting host path /Users/angelo/workspace/tmp/keycloak_certs into VM as /home/docker ...
    ▪ Mount type:   9p
    ▪ User ID:      docker
    ▪ Group ID:     docker
    ▪ Version:      9p2000.L
    ▪ Message Size: 262144
    ▪ Options:      map[]
    ▪ Bind Address: 192.168.64.1:57479
🚀  Userspace file server: ufs starting
✅  Successfully mounted /Users/angelo/workspace/tmp/keycloak_certs to /home/docker

📌  NOTE: This process must stay alive for the mount to be accessible ...

then ran minikube ssh:

❯ minikube ssh
ssh: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

also, ran minikube status:

❯ minikube status
E0201 20:10:19.375094   46711 status.go:417] failed to get storage capacity of /var: NewSession: new client: new client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
E0201 20:10:19.375149   46711 status.go:179] status error: NewSession: new client: new client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
E0201 20:10:19.375163   46711 status.go:126] status error: NewSession: new client: new client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

tried killing minikube mount process, but didn't resolve the ssh issue:

^C🔥  Unmounting /home/docker ...

❌  Exiting due to MK_INTERRUPTED: Received interrupt signal

❯ minikube ssh
ssh: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

Attach the log file

log.txt

Operating System

macOS (Default)

Driver

HyperKit

[angelosanramon]

Closing. This is my bad. The mount is overwriting the /home/docker directory. I thought it would create a keycloak_certs directory.

[Ritikaa96]

/close will close the issue @angelosanramon . thanks for updating.