"minikube service "anyservice" " command does not open default browser Ubuntu.

[OleksiiPasihnyk]

What Happened?

Steps to reproduce the issue:
I am trying to run the hello world service I deployed and exposed but after running "minikube service helloworld", I am getting an error message instead of minikube launching the service on my default browser.

linked issue

Attach the log file

log.txt

Operating System

Ubuntu

Driver

VirtualBox

[afbjorklund]

What is the error message ? If you run xdg-open with the URL, does it show anything ?

Examples

xdg-open 'http://www.freedesktop.org/'

Opens the freedesktop.org website in the user's default browser.

Also: xdg-settings get default-web-browser

[OleksiiPasihnyk]

#First command to check default settings
~$ xdg-settings get default-web-browser
$ google-chrome.desktop

#second command to check if deafault settings open the browser from console, yes it does open chrome.
~$ xdg-open 'http://www.freedesktop.org/'
~$ Fontconfig error: "/home/axelp/.fonts.conf", line 1: parsing XML declaration: '?>' expected

Opening in existing browser session.

[OleksiiPasihnyk]

If I run

$ minikube service list

I get proper responce which looks like a table and there is proper url link which is clickable and active and it does open in the browser properly.

[afbjorklund]

Sounds good. What was the error ?

[medyagh]

oks like a table and there is proper url link which is clickable and active and it does open in the browser properly.

I think when you click on it manually it will use your OS opening generic links

[henning]

I have the same issue, also on Ubuntu 22.04 but with the docker driver.

Version info:

$ minikube version
minikube version: v1.25.2
commit: 362d5fd

What do I expect?

I expect "minikube service SERVICENAME" to open a webbrowser, as it is documented here: https://minikube.sigs.k8s.io/docs/start/
I am really exactly trying to do what is described there in 4) - running and accessing the hello-minikube echo server.

What happens instead?
nothing at all. Neither does a browser open nor am I shown any message about an error.

I am pretty sure, my systems default browser config is fine, because "minikube dashboard" works as expected, opens the Browser with the dashboard.

Looking at "minikube help service" I get this information:

"Returns the Kubernetes URL(s) for service(s) in your local cluster. In the case of multiple URLs they will be printed
one at a time."

Which is not the same as what the tutorial says - but also not what really happens to me.

The part of making services accessible seems to work:
"minikube service list" lists URL's to access the service and manually entering them also works fine.

So it looks very much like "minikube service SERVICENAME" is just not giving proper output and also not starting the browser.

Also answering the xdg questions:

$ xdg-settings get default-web-browser
firefox_firefox.desktop

And

$ xdg-open 'http://www.freedesktop.org/'

shows the freedesktop page in my browser, just as "minikube dashboard" opens the dashboard in my browser.

[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

[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

[henning]

/remove-lifecycle rotten

[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

[henning]

/remove-lifecycle stale

[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

[henning]

/remove-lifecycle stale

On Wed 26. Apr 2023 at 12:41, Kubernetes Triage Robot < ***@***.***> wrote: 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 <https://www.kubernetes.dev/docs/guide/issue-triage/> Please send feedback to sig-contributor-experience at kubernetes/community <https://github.com/kubernetes/community>. /lifecycle stale — Reply to this email directly, view it on GitHub <#13985 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAJ2UEZDI7B4ZFN3JGH733XDD3XJANCNFSM5T2XEFXQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- Henning Sprang http://www.sprang.de

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