minikube dashboard

[RizalZulfiardi]

What Happened?

Log file created at: 2023/06/07 09:11:17
Running on machine: Rizal_Zulfiardi
Binary: Built with gc go1.20.2 for windows/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0607 09:11:17.624656 6348 out.go:296] Setting OutFile to fd 92 ...
I0607 09:11:17.625778 6348 out.go:309] Setting ErrFile to fd 96...
I0607 09:11:17.648464 6348 mustload.go:65] Loading cluster: minikube
I0607 09:11:17.649459 6348 config.go:182] Loaded profile config "minikube": Driver=docker, ContainerRuntime=docker, KubernetesVersion=v1.26.3
I0607 09:11:17.663004 6348 cli_runner.go:164] Run: docker container inspect minikube --format={{.State.Status}}
I0607 09:11:17.858891 6348 host.go:66] Checking if "minikube" exists ...
I0607 09:11:17.867164 6348 cli_runner.go:164] Run: docker container inspect -f "'{{(index (index .NetworkSettings.Ports "8443/tcp") 0).HostPort}}'" minikube
I0607 09:11:18.060262 6348 api_server.go:165] Checking apiserver status ...
I0607 09:11:18.068549 6348 ssh_runner.go:195] Run: sudo pgrep -xnf kube-apiserver.minikube.
I0607 09:11:18.074977 6348 cli_runner.go:164] Run: docker container inspect -f "'{{(index (index .NetworkSettings.Ports "22/tcp") 0).HostPort}}'" minikube
I0607 09:11:18.338528 6348 sshutil.go:53] new ssh client: &{IP:127.0.0.1 Port:1158 SSHKeyPath:C:\Users\Rizal.Zulfiardi.minikube\machines\minikube\id_rsa Username:docker}
W0607 09:11:18.489484 6348 api_server.go:169] stopped: unable to get apiserver pid: sudo pgrep -xnf kube-apiserver.minikube.: Process exited with status 1
stdout:

stderr:
I0607 09:11:18.495116 6348 out.go:177] 🤷 This control plane is not running! (state=Stopped)
W0607 09:11:18.499409 6348 out.go:239] ❗ This is unusual - you may want to investigate using "minikube logs"
I0607 09:11:18.502493 6348 out.go:177] 👉 To start a cluster, run: "minikube start"
Log file created at: 2023/06/07 10:20:52
Running on machine: Rizal_Zulfiardi
Binary: Built with gc go1.20.2 for windows/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0607 10:20:52.861103 10312 out.go:296] Setting OutFile to fd 100 ...
I0607 10:20:52.862103 10312 out.go:309] Setting ErrFile to fd 104...
I0607 10:20:52.886104 10312 mustload.go:65] Loading cluster: minikube
I0607 10:20:52.891103 10312 out.go:177] 🤷 Profile "minikube" not found. Run "minikube profile list" to view all profiles.
I0607 10:20:52.898103 10312 out.go:177] 👉 To start a cluster, run: "minikube start"
Log file created at: 2023/06/07 11:26:29
Running on machine: Rizal_Zulfiardi
Binary: Built with gc go1.20.2 for windows/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0607 11:26:29.733833 9112 out.go:296] Setting OutFile to fd 92 ...
I0607 11:26:29.743966 9112 out.go:309] Setting ErrFile to fd 96...
I0607 11:26:29.799529 9112 mustload.go:65] Loading cluster: minikube
I0607 11:26:29.812496 9112 config.go:182] Loaded profile config "minikube": Driver=docker, ContainerRuntime=docker, KubernetesVersion=v1.26.3
I0607 11:26:29.838351 9112 cli_runner.go:164] Run: docker container inspect minikube --format={{.State.Status}}
W0607 11:26:31.194927 9112 cli_runner.go:211] docker container inspect minikube --format={{.State.Status}} returned with exit code 1
I0607 11:26:31.194927 9112 cli_runner.go:217] Completed: docker container inspect minikube --format={{.State.Status}}: (1.3564161s)
I0607 11:26:31.210335 9112 out.go:177]
W0607 11:26:31.217227 9112 out.go:239] ❌ Exiting due to GUEST_STATUS: Unable to get machine status: state: unknown state "minikube": docker container inspect minikube --format=: exit status 1
stdout:

stderr:
error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/minikube/json": open //./pipe/docker_engine: The system cannot find the file specified.

W0607 11:26:31.218827 9112 out.go:239]
W0607 11:26:31.229350 9112 out.go:239] �[31m╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮�[0m
�[31m│�[0m �[31m│�[0m
�[31m│�[0m 😿 If the above advice does not help, please let us know: �[31m│�[0m
�[31m│�[0m 👉 https://github.com/kubernetes/minikube/issues/new/choose �[31m│�[0m
�[31m│�[0m �[31m│�[0m
�[31m│�[0m Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. �[31m│�[0m
�[31m│�[0m Please also attach the following file to the GitHub issue: �[31m│�[0m
�[31m│�[0m - C:\Users\RIZAL~1.ZUL\AppData\Local\Temp\minikube_dashboard_f3d1ee55395636a18a95c4eeeae1056906cb1ab4_0.log �[31m│�[0m
�[31m│�[0m �[31m│�[0m
�[31m╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯�[0m
I0607 11:26:31.235455 9112 out.go:177]
Log file created at: 2023/06/07 14:05:07
Running on machine: Rizal_Zulfiardi
Binary: Built with gc go1.20.2 for windows/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0607 14:05:07.004985 9372 out.go:296] Setting OutFile to fd 96 ...
I0607 14:05:07.096948 9372 out.go:309] Setting ErrFile to fd 100...
I0607 14:05:07.338300 9372 mustload.go:65] Loading cluster: minikube
I0607 14:05:07.434305 9372 config.go:182] Loaded profile config "minikube": Driver=docker, ContainerRuntime=docker, KubernetesVersion=v1.26.3
I0607 14:05:07.758334 9372 cli_runner.go:164] Run: docker container inspect minikube --format={{.State.Status}}
W0607 14:05:08.277194 9372 cli_runner.go:211] docker container inspect minikube --format={{.State.Status}} returned with exit code 1
I0607 14:05:08.313953 9372 out.go:177]
W0607 14:05:08.319944 9372 out.go:239] ❌ Exiting due to GUEST_STATUS: Unable to get machine status: state: unknown state "minikube": docker container inspect minikube --format=: exit status 1
stdout:

stderr:
Error response from daemon: No such container: minikube

W0607 14:05:08.320953 9372 out.go:239]
W0607 14:05:08.391878 9372 out.go:239] �[31m╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮�[0m
�[31m│�[0m �[31m│�[0m
�[31m│�[0m 😿 If the above advice does not help, please let us know: �[31m│�[0m
�[31m│�[0m 👉 https://github.com/kubernetes/minikube/issues/new/choose �[31m│�[0m
�[31m│�[0m �[31m│�[0m
�[31m│�[0m Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. �[31m│�[0m
�[31m│�[0m Please also attach the following file to the GitHub issue: �[31m│�[0m
�[31m│�[0m - C:\Users\RIZAL~1.ZUL\AppData\Local\Temp\minikube_dashboard_f3d1ee55395636a18a95c4eeeae1056906cb1ab4_0.log �[31m│�[0m
�[31m│�[0m �[31m│�[0m
�[31m╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯�[0m
I0607 14:05:08.399561 9372 out.go:177]
Log file created at: 2023/06/07 14:15:27
Running on machine: Rizal_Zulfiardi
Binary: Built with gc go1.20.2 for windows/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0607 14:15:27.303871 14248 out.go:296] Setting OutFile to fd 92 ...
I0607 14:15:27.306096 14248 out.go:309] Setting ErrFile to fd 96...
I0607 14:15:27.366813 14248 mustload.go:65] Loading cluster: minikube
I0607 14:15:27.369357 14248 config.go:182] Loaded profile config "minikube": Driver=docker, ContainerRuntime=docker, KubernetesVersion=v1.26.3
I0607 14:15:27.417210 14248 cli_runner.go:164] Run: docker container inspect minikube --format={{.State.Status}}
W0607 14:15:27.782663 14248 cli_runner.go:211] docker container inspect minikube --format={{.State.Status}} returned with exit code 1
I0607 14:15:27.788520 14248 out.go:177]
W0607 14:15:27.792748 14248 out.go:239] ❌ Exiting due to GUEST_STATUS: Unable to get machine status: state: unknown state "minikube": docker container inspect minikube --format=: exit status 1
stdout:

stderr:
Error response from daemon: No such container: minikube

W0607 14:15:27.792871 14248 out.go:239]
W0607 14:15:27.803892 14248 out.go:239] �[31m╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮�[0m
�[31m│�[0m �[31m│�[0m
�[31m│�[0m 😿 If the above advice does not help, please let us know: �[31m│�[0m
�[31m│�[0m 👉 https://github.com/kubernetes/minikube/issues/new/choose �[31m│�[0m
�[31m│�[0m �[31m│�[0m
�[31m│�[0m Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. �[31m│�[0m
�[31m│�[0m Please also attach the following file to the GitHub issue: �[31m│�[0m
�[31m│�[0m - C:\Users\RIZAL~1.ZUL\AppData\Local\Temp\minikube_dashboard_f3d1ee55395636a18a95c4eeeae1056906cb1ab4_0.log �[31m│�[0m
�[31m│�[0m �[31m│�[0m
�[31m╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯�[0m
I0607 14:15:27.808012 14248 out.go:177]

Attach the log file

minikube_dashboard_f3d1ee55395636a18a95c4eeeae1056906cb1ab4_0.log

Operating System

Windows

Driver

Docker

[ShardulPrabhu]

Is Docker deamon Running ?

[RizalZulfiardi]

Service docker running, alert "log" error, please help me, I installed tanzu to deploy vSphere but didn't get any credentials Pada tanggal Jum, 9 Jun 2023 04.58, ShardulPrabhu ***@***.***> menulis:

…

Is Docker deamon Running ? — Reply to this email directly, view it on GitHub <#16644 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ3IAAYYCFGMZ2THMOZUBIDXKJDJZANCNFSM6AAAAAAY5O5VBM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ShardulPrabhu]

Service docker running, alert "log" error, please help me, I installed tanzu to deploy vSphere but didn't get any credentials Pada tanggal Jum, 9 Jun 2023 04.58, ShardulPrabhu @.> menulis:
…
Is Docker deamon Running ? — Reply to this email directly, view it on GitHub <#16644 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ3IAAYYCFGMZ2THMOZUBIDXKJDJZANCNFSM6AAAAAAY5O5VBM . You are receiving this because you authored the thread.Message ID: @.>

Log in to your vSphere server.
Click on the "Home" icon in the vSphere client.
In the "Home" screen, click on the "Credentials" tab.
In the "Credentials" tab, click on the "Add" button.
In the "Add Credentials" dialog box, select the "VMware vSphere" type.
Enter the username and password for the vSphere server.
Click on the "OK" button.

[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

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