kind: better error output when docker isn't/can't log in

What would you like to be added: The ability get better error output in the non-default case when creating a new cluster and not specifying the default kind create cluster.

Why is this needed: I stumbled around for the better part of a week trying to understand why this didn’t work, below. only when I ran it as the default command did it appear to output the error – it’s picking up my docker login and I’d changed the password but had not re-logged in. After logging in properly, it is creating properly.

╭─ralph at surfacebook in ~/work/go/bin using
╰─○ kind create cluster --image=kindest/node:v1.14.0 --name kindly
Creating cluster "kindly" ...
 ✓ Ensuring node image (kindest/node:v1.14.0) 🖼
 ✓ Preparing nodes 📦
 ✓ Creating kubeadm config 📜
 ✗ Starting control-plane 🕹️
Error: failed to create cluster: failed to init node with kubeadm: exit status 1
╭─ralph at surfacebook in ~/work/go/bin using
╰─○ kind create cluster
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.14.2) 🖼
ERRO[17:42:25] Unable to find image 'kindest/node:v1.14.2@sha256:33539d830a6cf20e3e0a75d0c46a4e94730d78c7375435e6b49833d81448c319' locally
ERRO[17:42:25] docker: Error response from daemon: Get https://registry-1.docker.io/v2/kindest/node/manifests/sha256:33539d830a6cf20e3e0a75d0c46a4e94730d78c7375435e6b49833d81448c319: unauthorized: incorrect username or password.
ERRO[17:42:25] See 'docker run --help'.
 ✗ Preparing nodes 📦
ERRO[17:42:25] docker run error: exit status 125
Error: failed to create cluster: docker run error: exit status 125

About this issue

  • Original URL
  • State: open
  • Created 5 years ago
  • Reactions: 3
  • Comments: 15 (9 by maintainers)

Most upvoted comments

@BenTheElder this was why it was failing on my machine at KubeCon. 😃

What aojea said.

Sorry, we know this isn’t friendly, there’s just a LOT to do and initially we were targeting kubernetes (literally kubernetes itself) developers. There’s a lot to do. I have a sketch for more sophisticated help in the command but we’ve got some deep rework that needs doing to fix e.g. host reboot support first.