[질문 전 답변]1. 강의 내용과 관련된 질문인가요? [예 | 아니요]2. 인프런의 질문 게시판과 자주 하는 질문에 없는 내용인가요? [예 | 아니요]3. 질문 잘하기 법을 읽어보셨나요? [예 | 아니요](https://www.inflearn.com/blogs/1719)4. 잠깐! 인프런 서비스 운영 관련 문의는 1:1 문의하기를 이용해주세요.[질문 하기] 강사님께서 공유해주신 git에서 다운 받은 파일로 vagrant를 설정하는 도중에 다음과 같은 오류가 발생 했습니다.   내용 문의 드립니다.   m-k8s-1.20: [kubelet-check] Initial timeout of 40s passed. m-k8s-1.20: m-k8s-1.20: Unfortunately, an error has occurred: m-k8s-1.20: timed out waiting for the condition m-k8s-1.20: m-k8s-1.20: This error is likely caused by: m-k8s-1.20: - The kubelet is not running m-k8s-1.20: - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled) m-k8s-1.20: m-k8s-1.20: If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands: m-k8s-1.20: - 'systemctl status kubelet' m-k8s-1.20: - 'journalctl -xeu kubelet' m-k8s-1.20: m-k8s-1.20: Additionally, a control plane component may have crashed or exited when started by the container runtime. m-k8s-1.20: To troubleshoot, list all containers using your preferred container runtimes CLI. m-k8s-1.20: m-k8s-1.20: Here is one example how you may list all Kubernetes containers running in docker: m-k8s-1.20: - 'docker ps -a | grep kube | grep -v pause' m-k8s-1.20: Once you have found the failing container, you can inspect its logs with: m-k8s-1.20: - 'docker logs CONTAINERID' m-k8s-1.20: m-k8s-1.20: error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster m-k8s-1.20: To see the stack trace of this error execute with --v=5 or higher   OS : windows 10 virtualbox : 6.1  vagrant : last release