Cannot install minikube on Windows / Docker : Error dialing TCP: dial tcp 127.0.0.1:49204: connectex: No connection could be made because the target machine actively refused it.

kubernetes / minikube

Run Kubernetes locally

https://minikube.sigs.k8s.io/

Apache License 2.0

29.36k stars 4.88k forks source link

Cannot install minikube on Windows / Docker : Error dialing TCP: dial tcp 127.0.0.1:49204: connectex: No connection could be made because the target machine actively refused it. #10342

Closed noelwelsh closed 2 years ago

noelwelsh commented 3 years ago

I'm trying to install minikube on Windows 10 Home (10.0.19041 Build 19041) with Docker Desktop installed. The installation consistently fails at the minikube start command. The issue is that minikube cannot connect to the running docker instance. I have turned off the Microsoft Defender Firewall and closed my work VPN (CheckPoint) and the problem still persists.

Steps to reproduce the issue:

minikube delete --all
minikube start --alsologtostderr -v=5 2>minikube-err.txt

Full output of failed command: 😄 minikube v1.17.1 on Microsoft Windows 10 Home 10.0.19041 Build 19041 ✨ Using the docker driver based on existing profile 👍 Starting control plane node minikube in cluster minikube 🏃 Updating the running docker "minikube" container ... 🏃 Updating the running docker "minikube" container ...

Full output of minikube start command used, if not already included:

The logs saved in minikube-err.txt are in a gist.

Other

I tried to ssh to the same host and post as minikube:

> ssh  127.0.0.1 -p 49208
ssh: connect to host 127.0.0.1 port 49208: Connection refused

TIA!

omjadas commented 3 years ago

Also experiencing the same issue on Windows 10 with the Docker driver

priyawadhwa commented 3 years ago

Hey @noelwelsh thanks for opening this issue. Looks like the failing error is:

W0202 13:05:54.378261    6584 out.go:181] ÔØî  Exiting due to GUEST_PROVISION: Failed to start host: provision: Temporary Error: 
NewSession: new client: new client: dial tcp 127.0.0.1:49208: connectex: No connection could be made because the target machine 
actively refused it.

which seems similar to https://github.com/kubernetes/minikube/issues/7549. Based on https://github.com/kubernetes/minikube/issues/7549#issuecomment-611595010 looks like it is an issue with your firewall. Unfortunately, I'm not sure what more you can do besides turning it off since I'm not very familiar with Windows, but perhaps that thread will have something useful.

k8s-triage-robot commented 3 years ago

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

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

/lifecycle stale

ffroliva commented 3 years ago

I am also facing this issue.

Can this be related to lack of HD space?

sharifelgamal commented 3 years ago

We have separate checks to make sure there is enough disk space dedicated to docker and will generally error out with a special message if there isn't enough space.

We have made a bunch of changes to the docker driver on windows in the past few months, so this issue might not happen as frequently or, hopefully, at all.

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

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

/lifecycle rotten

noelwelsh commented 2 years ago

/close

k8s-ci-robot commented 2 years ago

@noelwelsh: Closing this issue.

In response to [this](https://github.com/kubernetes/minikube/issues/10342#issuecomment-1012495676): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.