minikube start times out (docker ssh connection refused)

[ThisDevDane]

What Happened?

Since a couple of weeks ago I can't start any minikube profiles.
It will fail on trying to dial sshd inside the container which refuses the connection for some reason

Even when trying to ssh in manually;

❯ ssh 127.0.0.1 -p 64969
ssh: connect to host 127.0.0.1 port 64969: Connection refused
❯ ssh localhost -p 64969
ssh: connect to host localhost port 64969: Connection refused

For extra context this is done using Docker Desktop and WSL2.

Attaching into the container and looking for ports it's listening to it does seem sshd is bound to port 22 which is exported to port 64969 by docker

Inside the kicbase container
# ss -tupln
Netid     State      Recv-Q      Send-Q           Local Address:Port            Peer Address:Port     Process                                   
udp       UNCONN     0           0                   127.0.0.11:35389                0.0.0.0:*                                                  
tcp       LISTEN     0           4096                127.0.0.11:42417                0.0.0.0:*                                                  
tcp       LISTEN     0           128                    0.0.0.0:22                   0.0.0.0:*         users:(("sshd",pid=125,fd=3))            
tcp       LISTEN     0           4096              192.168.49.2:10010                0.0.0.0:*         users:(("containerd",pid=110,fd=12))     
tcp       LISTEN     0           128                       [::]:22                      [::]:*         users:(("sshd",pid=125,fd=4))

WSL2
❯ docker ps
CONTAINER ID   IMAGE                                 COMMAND                  CREATED         STATUS         PORTS                                                                                                                                  NAMES
363dd023bf69   gcr.io/k8s-minikube/kicbase:v0.0.39   "/usr/local/bin/entr…"   5 minutes ago   Up 5 minutes   127.0.0.1:64969->22/tcp, 127.0.0.1:64970->2376/tcp, 127.0.0.1:64967->5000/tcp, 127.0.0.1:64968->8443/tcp, 127.0.0.1:64971->32443/tcp   HB1
c83c26b60bf3   postgres:15-alpine                    "docker-entrypoint.s…"   12 days ago     Up 2 hours     0.0.0.0:5432->5432/tcp                                                                                                                 src_db_1
a1836e3ce4bc   redis:alpine                          "docker-entrypoint.s…"   12 days ago     Up 2 hours     0.0.0.0:6379->6379/tcp                                                                                                                 src_redis_1

A difference from other containers where I expose ports is that minikube ports are specifically bound to 127.0.0.1 and other containers bind to 0.0.0.0 which might have some conflict when running over WSL2?

(While waiting for the timeout to occur it also recreated the container with new ports, 65099, but it had the same problem)

Attach the log file

log.txt

Operating System

Windows

Driver

Docker

[everflux]

Are you by any chance using the experimental WASM feature?

[ThisDevDane]

As far as I am aware, I am not. I have since gone from using Docker Desktop and instead directly install docker on my debian wsl2 instance and it now works since the 127.0.0.1 is not another instance like it is on Docker Desktop

[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/test-infra repository.