jeanluclariviere

@cpuguy83 @mikebrow sorry, I only mention crictl to demonstrate that the credentials are working. I don't think we should get hung up on the fact that I used it to...

> please add -D to crictl and let's see which container runtime it is connecting to.. if crictl is connecting via the containerd daemon.. then it is working as designed....

@cpuguy83 Ok, so I've configured a bare-metal kubeadm Kubernetes cluster with containerd as the runtime. I've configured this cluster to to pull it's control plane images from a private repo...

@mikebrow Thanks for the update - so what you're saying is that a kubernetes cluster with containerd as its runtime environment will not leverage the `config.toml` to pull down its...

> after modifying the config.toml you have to restart your containerd service I restarted containerd each time I modified the `config.toml`

Further to this, I just wanted to add that if I try to pull the images down directly with **kubeadm**, the images fail with an unauthorized response - it's as...

I'll raise an issue with the kubeadm team to see if they can't corroborate that. In the meantime, can you confirm if crictl should be able to pull images down...

Sorry if I'm not being clear - let me be more specific. If I run either of the following commands, specifying the --creds or --auth **flags**, the image is pulled...

@mikebrow Thanks a bunch for linking me to the official documentation, using it I was able to solve my problem. I'm guessing the syntax must have changed over the years,...

@brancz sorry, I've been meaning to get back to this but I keep getting side tracked with other things. Do you think the Troubleshooting section on the main page would...