Skip to content

Error message in K8S_APISERVER_MISSING #20518

Open
@Ret2Me

Description

@Ret2Me

What Happened?

Hi, after update of the Docker Desktop for MacOS (Apple Silicon) I came across following issue (img at the bottom).
Even after multiple restarts (PC, Docker and minikube) error still occur.

In the suggestions at the end of the error message I found information about probable problems with SELinux but that was not a issue.
I tried many things and only one solved my issue, I had to delete cluster minikube delete.

Maybe it would be a good idea to link this issue and add this solution to list at the bottom of the error message.

Attach the log file

I already solved this problem so every thing that I got is this error message from the terminal

Image

Operating System

macOS (Default)

Driver

Docker

Activity

Ret2Me

Ret2Me commented on Mar 10, 2025

@Ret2Me
Author

I can try to do it myself and add pull request but I would like someones approval on this idea.

dhairya-seth

dhairya-seth commented on Mar 11, 2025

@dhairya-seth

Hi @Ret2Me, minikube error logs mainly provide suggestions about what went wrong so that we can do troubleshooting (based on that) to resolve the error. Including the suggested solution in the error log might be a good way.

dhairya-seth

dhairya-seth commented on Mar 11, 2025

@dhairya-seth

It would be great to take feedback from higher community members on this before raising pr.

k8s-triage-robot

k8s-triage-robot commented on Jun 9, 2025

@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

added
lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
on Jun 9, 2025
k8s-triage-robot

k8s-triage-robot commented on Jul 9, 2025

@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

added
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
on Jul 9, 2025
Ret2Me

Ret2Me commented on Jul 10, 2025

@Ret2Me
Author

/remove-lifecycle rotten

removed
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
on Jul 10, 2025
Ret2Me

Ret2Me commented on Jul 10, 2025

@Ret2Me
Author

Issue is still active

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @k8s-ci-robot@Ret2Me@k8s-triage-robot@dhairya-seth

      Issue actions

        Error message in K8S_APISERVER_MISSING · Issue #20518 · kubernetes/minikube