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

Deploying to of a container/pod to a Kubernetes Error: read ECONNRESET #45

Closed
odockal opened this issue May 28, 2024 · 6 comments · Fixed by #50
Closed

Deploying to of a container/pod to a Kubernetes Error: read ECONNRESET #45

odockal opened this issue May 28, 2024 · 6 comments · Fixed by #50
Assignees

Comments

@odockal
Copy link

odockal commented May 28, 2024

I have minikube cluster started via Podman Desktop 1.10.3 with 0.0.3 minikube extension.
I have managed to create a minikube cluster, but any of my attempts to deploy any container or pod to the cluster fails on: Error: read ECONNRESET. Without any other specific error stack trace.

If I switch a kubecontext to a minikube, I can see this in console:

main ↪️ Error while fetching API groups: Error: read ECONNRESET
main ↪️ Kube pod watch ended Error: read ECONNRESET

On cli using kubectl:

kubectl get pods -A
E0528 08:59:59.485001 1125359 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:45563/api?timeout=32s": read tcp 127.0.0.1:34034->127.0.0.1:45563: read: connection reset by peer - error from a previous attempt: read tcp 127.0.0.1:34020->127.0.0.1:45563: read: connection reset by peer
@odockal
Copy link
Author

odockal commented Jun 4, 2024

I am able to reproduce the issue now:
The problem is that I tried to restart minikube cluster using Podman Desktop which led to a situation, where it seems on PD side that everything is fine, the status of the cluster is RUNNING, but the truth is that it is not.

  1. Start up Minikube cluster
  2. Assert it is started
  3. Switch context to the minikube
  4. Test kubectl get pods -A via cli
  5. Restart minikube using Podman Desktop
  6. Assert: Minikube is started
    Screenshot_20240604_115856
  7. Check kubectl get pods -A
    Actual result:
kubectl get pods -A
Get "https://127.0.0.1:42373/api/v1/pods?limit=500": read tcp 127.0.0.1:35198->127.0.0.1:42373: read: connection reset by peer - error from a previous attempt: read tcp 127.0.0.1:35192->127.0.0.1:42373: read: connection reset by peer

Then if you try to deploy to kubernetes, you get ERROR: ECONNRESET.

Only workaround seems to remove and recreate the cluster from scratch.

@nichjones1 nichjones1 moved this from 📋 Backlog to 📅 Planned in Podman Desktop Planning Jun 4, 2024
@lstocchi lstocchi moved this from 📅 Planned to 🚧 In Progress in Podman Desktop Planning Jun 12, 2024
@lstocchi lstocchi moved this from 🚧 In Progress to 🚥 In Review in Podman Desktop Planning Jun 12, 2024
@github-project-automation github-project-automation bot moved this from 🚥 In Review to ✔️ Done in Podman Desktop Planning Jul 2, 2024
@slemeur
Copy link

slemeur commented Nov 6, 2024

Should we reopen it @odockal ?

@odockal
Copy link
Author

odockal commented Nov 7, 2024

@slemeur Afaik the fix was never released. If we release the extension with fix, it should be good then.

@odockal
Copy link
Author

odockal commented Nov 7, 2024

We have epic opened: #148, maybe we just need to give it more priority.

@slemeur
Copy link

slemeur commented Nov 7, 2024

Ok - thanks!

@odockal
Copy link
Author

odockal commented Nov 8, 2024

Not sure about windows and Mac, but on Linux this does not happen at all with 0.4.0.

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 a pull request may close this issue.

3 participants