It seems that this error has been lifted to be a fatal one with Kubernetes 1.10. I cannot get a 1.10.2 kubelet running at the moment.