❌ Exiting due to HOST_BROWSER: open url failed: [default my-app-service http://127.0.0.1:38349]: exit status 3

[sameer1098alam]

What Happened?

-----------|----------------|-------------|------------------------|
🎉 Opening service default/my-app-service in default browser...
/usr/bin/xdg-open: 882: x-www-browser: not found
/usr/bin/xdg-open: 882: firefox: not found
/usr/bin/xdg-open: 882: iceweasel: not found
/usr/bin/xdg-open: 882: seamonkey: not found
/usr/bin/xdg-open: 882: mozilla: not found
/usr/bin/xdg-open: 882: epiphany: not found
/usr/bin/xdg-open: 882: konqueror: not found
/usr/bin/xdg-open: 882: chromium: not found
/usr/bin/xdg-open: 882: chromium-browser: not found
/usr/bin/xdg-open: 882: google-chrome: not found
/usr/bin/xdg-open: 882: www-browser: not found
/usr/bin/xdg-open: 882: links2: not found
/usr/bin/xdg-open: 882: elinks: not found
/usr/bin/xdg-open: 882: links: not found
/usr/bin/xdg-open: 882: lynx: not found
/usr/bin/xdg-open: 882: w3m: not found
xdg-open: no method available for opening

Attach the log file

s

Operating System

Ubuntu

Driver

Docker

[T-Lakshmi]

@sameer1098alam,
Please attach complete logs to get clear understanding on issue you are facing.

Run minikube logs --file=logs.txt and attach logs.txt file in description.

[T-Lakshmi]

/triage needs-informatin

[k8s-ci-robot]

@T-Lakshmi: The label(s) triage/needs-informatin cannot be applied, because the repository doesn't have them.

In response to this:

/triage needs-informatin

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.

[T-Lakshmi]

/triage needs-information

[Ritikaa96]

Similar issue: #10163

[Ritikaa96]

You can find the meaning of error code and self troubleshoot using https://minikube.sigs.k8s.io/docs/contrib/errorcodes/. Please go through the guides once and as stated above add logs for better solution.

[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