add environment diagnostics

kubernetes-sigs / kind

Kubernetes IN Docker - local clusters for testing Kubernetes

https://kind.sigs.k8s.io/

Apache License 2.0

13.37k stars 1.55k forks source link

add environment diagnostics #39

Open BenTheElder opened 6 years ago

BenTheElder commented 6 years ago

we should have a number of checks when kind fails, to help diagnose issues in the environment, ideally this can also be invoked by another command, some rough ideas:

[ ] check if there are existing containers tagged with the current cluster when creating
[ ] more gracefully handle lack of cluster artifacts when deleting
[ ] gracefully handle incompatible docker / lack of docker
[ ] base image builds should check that go exists

/priority important-soon

BenTheElder commented 5 years ago

/assign The "cluster already exists" / "no cluster exists" for create and delete would be nice to get into our first release.

BenTheElder commented 5 years ago

/lifecycle active

BenTheElder commented 5 years ago

this work is now stale, will come back to it later

BenTheElder commented 5 years ago

I beleive @neolit123 added the "existing cluster name" check

alejandrox1 commented 5 years ago

haven't been participating as much as I'd like to but i'd like to get back to a more regular workflow and start working on this. I'll get something for handling incompatible/lack of docker :slightly_smiling_face:

aojea commented 5 years ago

@BenTheElder please add a check for IPv6 if IPfamily with IPv6 to the list😅 it took me 30 mins to realize it was failing because the docker daemon didn´t have IPv6 enabled

stmcginnis commented 5 months ago

Another possible check - we've had some issues due to DOCKER_DEFAULT_PLATFORM being set. Could include a check for that as a data point when collecting troubleshooting data.

Another common issue could be helped with collecting any available Docker/Docker Desktop information.