갑자기 회사에서 맥북을 지급받게되었다.
그러면서 또 갑자기 k8s기반 (AWS EKS) 시스템을 운영하게 되어,
Local에서 테스트할 환경을 만들고자, 처음 사용해보는 맥북에다가, 졸지에 k8s 환경까지 세팅하게되었다.
회사 방침상 docker 를 사용할 수 없어서,
대체제를 찾아보다아 podman 이라는 컨테이너 엔진을 발견하고,
설치하였다.
찾아서 찾아서, brew도 깔고.. .그걸로 minikube, podman, 쿠버네티스cli 등을 설치하고,
minikube start --driver=podman
으로 올리는데, 아오 계속 아래와 같은 이상한 에러가 발생하고 앉았음.
---------------------------------------------------------------------------------------------------
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in docker:
- 'docker ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'docker logs CONTAINERID'
stderr:
[WARNING FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables does not exist
[WARNING SystemVerification]: this Docker version is not on the list of validated versions: 24.0.7. Latest validated version: 20.10
[WARNING SystemVerification]: missing optional cgroups: hugetlb
[WARNING SystemVerification]: missing required cgroups: cpuset
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
💡 권장: Check output of 'journalctl -xeu kubelet', try passing --extra-config=kubelet.cgroup-driver=systemd to minikube start
🍿 관련 이슈: https://github.com/kubernetes/minikube/issues/4172
----------------------------------------------------------------------------------------------------------
minikube가 친절하게, 깃헙의 관련 이슈 링크도 해주고 하지만, 그 방법대로 안되더라...
지우고 설치하기를 반복하다가 결국... 문제를 발견함.
podman 스타트할때 root권한을 안줘서 그럼
그래서
podman machine stop
podman machine set --rootful
podman machine start
으로 성공...
하찮은 이거땜에 하루날려먹음....
그래도 다행이야... 빙산의 일각중, 일각이 지나가서...