Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minikube cluster not visible on the Resources page when created with Podman driver in Podman Desktop #152

Open
amisskii opened this issue Oct 10, 2024 · 5 comments
Labels
kind/bug 🐞 Something isn't working

Comments

@amisskii
Copy link
Contributor

amisskii commented Oct 10, 2024

When creating a Minikube cluster via Podman Desktop with the default driver set to Podman, the cluster information and control buttons do not appear on the Resources page, and there is no Minikube container listed on the Containers page. However, if the Minikube cluster is created using the Docker driver, the cluster is visible on the Resources page, and a Minikube container is also visible.

Extension version: v0.3.0
OS: Fedora 40

Steps to reproduce:

  1. Install the Minikube extension.
  2. Install Minikube CLI
    minikube should run in rootful mode
  3. Navigate to Settings → Resources page.
  4. Go to the Minikube cluster creation page.
  5. Ensure the Podman driver is selected.
  6. Create the Minikube cluster.

Image

@amisskii amisskii added the kind/bug 🐞 Something isn't working label Oct 10, 2024
@afbjorklund
Copy link
Contributor

afbjorklund commented Nov 2, 2024

The code is looking for the label name.minikube.sigs.k8s.io on the node container.

Note that by default minikube uses the system podman, while PD shows user podman:

https://minikube.sigs.k8s.io/docs/drivers/podman/#rootless-podman


If you deployed rootless with Docker, you would probably have the same issue?

Since Podman Desktop can only show system docker, but not the user docker...

https://docs.docker.com/engine/security/rootless/

@amisskii
Copy link
Contributor Author

amisskii commented Nov 8, 2024

@afbjorklund Thank you for your comment. I've tried to investigate it further, but it seems that when I deploy a Minikube cluster with the system Podman, it still doesn't appear.

@afbjorklund
Copy link
Contributor

Does it appear in sudo podman ps in the terminal?

@amisskii
Copy link
Contributor Author

Yes, there is log output:

sudo podman ps
CONTAINER ID  IMAGE                                COMMAND     CREATED        STATUS        PORTS                                                                                                                                                   NAMES
d93ae3067ce0  gcr.io/k8s-minikube/kicbase:v0.0.45              2 minutes ago  Up 2 minutes  127.0.0.1:39645->22/tcp, 127.0.0.1:46529->2376/tcp, 127.0.0.1:37253->5000/tcp, 127.0.0.1:39475->8443/tcp, 127.0.0.1:38349->32443/tcp, 22/tcp, 8443/tcp  minikube

However, I don't see it on the resources page or as a container on the containers page.

On the Kubernetes page, it shows that I'm connected to the cluster, and I can see the running cluster node.

@amisskii
Copy link
Contributor Author

The issue was caused by my local Minikube configuration. Setting Minikube to rootless mode solved it: minikube config set rootless true

@amisskii amisskii reopened this Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug 🐞 Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants