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

fix: use minikube cli to start/stop cluster #50

Merged
merged 2 commits into from
Jul 2, 2024

Conversation

lstocchi
Copy link
Contributor

This resolves #45

So far we were starting the existing minikube cluster just by starting/stopping the minikube container. Unfortunately this is not enough. Even though the container was started, the minikube cluster remained stopped.

The minikube start command is responsible to start all features and handle all the process.

lstocchi added 2 commits June 12, 2024 14:36
So far we were starting the existing minikube cluster just by
starting/stopping the minikube container. Unfortunately this is not
enough. Even though the container was started, the minikube cluste was
stopped. The minikube start command is responsible to start all features and handle all the process.
Signed-off-by: lstocchi <[email protected]>
@lstocchi lstocchi marked this pull request as ready for review June 12, 2024 13:08
@lstocchi lstocchi requested review from benoitf and a team as code owners June 12, 2024 13:08
@lstocchi
Copy link
Contributor Author

@odockal it would be great if you could confirm it actually fixes the problem. I followed your steps to replicate it but just to be sure. Thanks!!

Copy link
Contributor

@jeffmaury jeffmaury left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lstocchi lstocchi merged commit 7a22d5b into podman-desktop:main Jul 2, 2024
4 checks passed
@lstocchi lstocchi deleted the i45 branch July 2, 2024 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Deploying to of a container/pod to a Kubernetes Error: read ECONNRESET
2 participants