minikube tunnel is asking for a password but not sure what password this is?

[reuben-tonna-ixaris]

I am experimenting with minikube on windows 10 using docker for windows and following https://minikube.sigs.k8s.io/docs/start/ steps to get a sample cluster up and running.

I would like to try out the load balanced deployments, however when in a command prompt started as 'administrator' (or not) I type in minikube tunnel I get the following:

C:\Windows\system32>minikube tunnel

• Starting tunnel for service balanced.
  [email protected]'s password:

The problem is that I do not have a clue what password it is expecting? Can you clarify please? Well I did try some docker for windows related passwords but none worked.

Interestingly even with the above the external ip is assigned:

C:\Users\reuben.tonna>kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
balanced LoadBalancer 10.99.196.66 127.0.0.1 8080:32238/TCP 9m8s

But, trying to navigate to localhost:8080 in a browser I get a "connection refused" error.

I tried to clear the state with a minikube delete and recreating the balanced deployment but still the same error.

[RA489]

/kind support

[antoinemerle]

Seems related to the same issue here : #9971 . Even if OP did not respond to the maintainers.

Here is some info. Dunno if that may help, but I am facing the same issue using :
minikube tunnel

Instead I tried doing
minikube service <name-of-the-service>

what I got is

* Restarting the docker service may improve performance.
|-----------|----------------|-------------|---------------------------|
| NAMESPACE |      NAME      | TARGET PORT |            URL            |
|-----------|----------------|-------------|---------------------------|
| default   | <name-of-the-service> |        5432 | http://192.168.49.2:32275 |
|-----------|----------------|-------------|---------------------------|
* Starting tunnel for service <name-of-the-service>.
[email protected]'s password: |-----------|----------------|-------------|------------------------|
| NAMESPACE |      NAME      | TARGET PORT |          URL           |
|-----------|----------------|-------------|------------------------|
| default   | <name-of-the-service> |             | http://127.0.0.1:61962 |
|-----------|----------------|-------------|------------------------|
* Opening service default/<name-of-the-service> in default browser...
! Because you are using a Docker driver on windows, the terminal needs to be open to run it

Accessing http://127.0.0.1:61962 : I got "connection refused"
Accessing http://192.168.49.2:32275 : I got a timeout error

I got the same "issue" using :

• windows 10
• minikube for windows
• docker as driver
• kubectl

best,

[k8s-triage-robot]

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

[RA489]

/remove-lifecycle stale

[k8s-triage-robot]

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

[RA489]

/remove-lifecycle stale

[drewhagen]

I'm running into this issue as well.

[k8s-triage-robot]

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

[RA489]

/remove-lifecycle stale

[k8s-triage-robot]

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

[RA489]

/remove-lifecycle stale

[k8s-triage-robot]

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

[peccu]

Maybe you can set the password for the user docker like below.
But I don't know if that will solve the problem.

$ minikube ssh
docker@minikube:~$ sudo su -
root@minikube:~# passwd docker
New password:    # <-- you can set any password
Retype new password:
passwd: password updated successfully
root@minikube:~# logout
docker@minikube:~$ logout
$ minikube tunnel
Starting tunnel for service balanced.
[email protected]'s password:  # <-- this should accept above password

[pclaudinoo]

@peccu 's solution made it for me

[k8s-triage-robot]

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

[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.

[bergstenarn]

/reopen

[k8s-ci-robot]

@bergstenarn: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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.

[bergstenarn]

I still experience the problem so it would be nice if the ticket could be reopened.

[pooransuthar1999]

Same for me

[Style5000]

Same issue here!

[Style5000]

/reopen

[k8s-ci-robot]

@Style5000: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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.

[danneu]

This happens when you're mapping a privileged port like port 80 to a container.

apiVersion: v1
kind: Service
metadata:
  name: foo
spec:
  type: LoadBalancer
  selector:
    app: foo
  ports:
  # - port: 80 # External
  - port: 4000 # External
    targetPort: 4000

In development (minikube) you can use an unprivileged port. And when deploying to production (like to GPE), you can change kubernetes.yaml map it back to port 80.

I'm no guru. I just ran into the password issue on minikube tunnel after forgetting that I was mapping port 80 which i only do in production.