Exiting due to HOST_BROWSER: open url failed: [default krscitizen http://127.0.0.1:57876]: The operation attempted is not supported.

[vaishu16003]

What Happened?

• Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue.
• Please also attach the following file to the GitHub issue:
• • C:\WINDOWS\SystemTemp\minikube_service_40f50f1cf674de1b5f72ed9c75c4195807196358_0.log

Attach the log file

minikube_service_40f50f1cf674de1b5f72ed9c75c4195807196358_0.log

Operating System

Windows

Driver

Docker

[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

[Ritikaa96]

/kind support

[Ritikaa96]

Hi @vaishu16003 seems like this issue is similar to : #11222 this past issue.
did you set the value of $HOST_BROWSER? in the logs the ports are different

I0714 13:00:32.099700 24812 ssh_conn.go:187] kubernetes tunnel: Warning: Permanently added '[127.0.0.1]:64518' (ED25519) to the list of known hosts.
I0714 13:00:32.137884 24812 ssh_conn.go:187] mysql tunnel: Warning: Permanently added '[127.0.0.1]:64518' (ED25519) to the list of known hosts.
I0714 13:00:33.133041 24812 out.go:177] * Opening service default/krscitizen in default browser...
I0714 13:00:34.263560 24812 out.go:177]
W0714 13:00:34.292174 24812 out.go:239] X Exiting due to HOST_BROWSER: open url failed: [default krscitizen http://127.0.0.1:64674]: The operation attempted is not supported.

[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-sigs/prow repository.