[질문 전 답변]
1. 강의에서 다룬 내용과 관련된 질문인가요? [예 | 아니요]
2. 인프런의 질문 게시판과 자주 하는 질문에 없는 내용인가요? [예 | 아니요]
3. 질문 잘하기 법을 읽어보셨나요? [예 | 아니요]
(https://www.inflearn.com/blogs/1719)
4. 잠깐! 인프런 서비스 운영 관련 문의는 1:1 문의하기를 이용해주세요.
[질문 하기]
'1.2. 코드로 쉽게 구성하는 쿠버네티스 랩 환경' 과정 진행 중 vagrant up 에서 에러가 발생하였습니다.
관련하여 도움을 받을 수 있는 부분이 있을까 하여 문의드립니다.
1. 워커 노드가 구성되는 과정에서 다음 에러가 발생하면서 vagrant 실행이 중단되는 것을 보았습니다.
https://192.168.1.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s": dial tcp 192.168.1.10:6443: connect: connection refused
[로그]
-----------------------------------------------
w1-k8s-1.20: Dependency Installed: w1-k8s-1.20: conntrack-tools.x86_64 0:1.4.4-7.el7 w1-k8s-1.20: cri-tools.x86_64 0:1.23.0-0 w1-k8s-1.20: kubernetes-cni.x86_64 0:0.8.7-0 w1-k8s-1.20: libnetfilter_cthelper.x86_64 0:1.0.0-11.el7 w1-k8s-1.20: libnetfilter_cttimeout.x86_64 0:1.0.0-7.el7 w1-k8s-1.20: libnetfilter_queue.x86_64 0:1.0.2-2.el7_2 w1-k8s-1.20: socat.x86_64 0:1.7.3.2-2.el7 w1-k8s-1.20: Complete! w1-k8s-1.20: Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service. w1-k8s-1.20: Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /usr/lib/systemd/system/kubelet.service. ==> w1-k8s-1.20: Running provisioner: shell... w1-k8s-1.20: Running: C:/Users/sunba/AppData/Local/Temp/vagrant-shell20220504-9152-agv56t.sh w1-k8s-1.20: [preflight] Running pre-flight checks w1-k8s-1.20: [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/ w1-k8s-1.20: error execution phase preflight: couldn't validate the identity of the API Server: Get "https://192.168.1.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s": dial tcp 192.168.1.10:6443: connect: connection refused
2. 위 내용을 확인한 이후 마스터 노드가 구성될때의 로그를 확인 시 다음 에러가 먼저 발생했던 것으로 확인하였습니다.
[ERROR ImagePull]: failed to pull image k8s.gcr.io/etcd:3.4.13-0: output: 3.4.13-0: Pulling from etcd
filesystem layer verification failed for digest sha256:6937ebe10f0225ac2ef529a733a02d46829421411fb9e33145f19d4026d75478
kubeadm init 실행 중에 발생한 것 같은데, VM 에 직접 접속하여 동일한 명령을 실행했을 시에도 같은 에러를 확인할 수 있었습니다.
해당 과정이 정상적으로 진행되지 않아 이후 내용에서 에러가 발생하는 것으로 판단하고 있습니다.
[로그] ----------------------------------------------- ==> m-k8s-1.20: Running provisioner: shell... m-k8s-1.20: Running: C:/Users/sunba/AppData/Local/Temp/vagrant-shell20220504-9152-1vs2oye.sh m-k8s-1.20: I0504 21:41:56.350942 3297 version.go:251] remote version is much newer: v1.24.0; falling back to: stable-1.20 m-k8s-1.20: [init] Using Kubernetes version: v1.20.15 m-k8s-1.20: [preflight] Running pre-flight checks m-k8s-1.20: [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/ m-k8s-1.20: [preflight] Pulling images required for setting up a Kubernetes cluster m-k8s-1.20: [preflight] This might take a minute or two, depending on the speed of your internet connection m-k8s-1.20: [preflight] You can also perform this action in beforehand using 'kubeadm config images pull' m-k8s-1.20: error execution phase preflight: [preflight] Some fatal errors occurred: m-k8s-1.20: [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.20.15: output: v1.20.15: Pulling from kube-apiserver m-k8s-1.20: 0d7d70899875: Pulling fs layer m-k8s-1.20: d373bafe570e: Pulling fs layer m-k8s-1.20: bd216676f0c7: Pulling fs layer m-k8s-1.20: 0d7d70899875: Verifying Checksum m-k8s-1.20: d373bafe570e: Verifying Checksum m-k8s-1.20: d373bafe570e: Download complete m-k8s-1.20: bd216676f0c7: Verifying Checksum m-k8s-1.20: filesystem layer verification failed for digest sha256:bd216676f0c74b2c08653aefec1786b044600c23e9c0bfec66a1471d9e202153 m-k8s-1.20: , error: exit status 1 m-k8s-1.20: [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-controller-manager:v1.20.15: output: v1.20.15: Pulling from kube-controller-manager m-k8s-1.20: 0d7d70899875: Pulling fs layer m-k8s-1.20: d373bafe570e: Pulling fs layer m-k8s-1.20: 65c97745feee: Pulling fs layer m-k8s-1.20: d373bafe570e: Verifying Checksum m-k8s-1.20: 0d7d70899875: Verifying Checksum m-k8s-1.20: 0d7d70899875: Download complete m-k8s-1.20: 0d7d70899875: Pull complete m-k8s-1.20: 65c97745feee: Verifying Checksum m-k8s-1.20: filesystem layer verification failed for digest sha256:65c97745feeedee0d01b9c4c903e0bc020557314cea66e08076290358687651b m-k8s-1.20: , error: exit status 1 m-k8s-1.20: [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-scheduler:v1.20.15: output: v1.20.15: Pulling from kube-scheduler m-k8s-1.20: 0d7d70899875: Pulling fs layer m-k8s-1.20: d373bafe570e: Pulling fs layer m-k8s-1.20: f178a26415ce: Pulling fs layer m-k8s-1.20: 0d7d70899875: Verifying Checksum m-k8s-1.20: 0d7d70899875: Download complete m-k8s-1.20: d373bafe570e: Verifying Checksum m-k8s-1.20: d373bafe570e: Download complete m-k8s-1.20: 0d7d70899875: Pull complete m-k8s-1.20: f178a26415ce: Verifying Checksum m-k8s-1.20: d373bafe570e: Pull complete m-k8s-1.20: filesystem layer verification failed for digest sha256:f178a26415ceb0f8201c78c9629b92b299f198324f498f96d3d8c614ae7c2fcd m-k8s-1.20: , error: exit status 1 m-k8s-1.20: [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-proxy:v1.20.15: output: v1.20.15: Pulling from kube-proxy m-k8s-1.20: 20b09fbd3037: Pulling fs layer m-k8s-1.20: be5cda1e916d: Pulling fs layer m-k8s-1.20: be5cda1e916d: Verifying Checksum m-k8s-1.20: filesystem layer verification failed for digest sha256:be5cda1e916d7a8a6ae0d561d3d18bd3daf5fe4a45cc8a998aa0c12a0794782d m-k8s-1.20: , error: exit status 1 m-k8s-1.20: [ERROR ImagePull]: failed to pull image k8s.gcr.io/etcd:3.4.13-0: output: 3.4.13-0: Pulling from etcd m-k8s-1.20: Get https://k8s.gcr.io/v2/etcd/manifests/sha256:bd4d2c9a19be8a492bc79df53eee199fd04b415e9993eb69f7718052602a147a: tls: invalid certificate signature m-k8s-1.20: , error: exit status 1 m-k8s-1.20: [ERROR ImagePull]: failed to pull image k8s.gcr.io/coredns:1.7.0: output: 1.7.0: Pulling from coredns m-k8s-1.20: c6568d217a00: Pulling fs layer m-k8s-1.20: 6937ebe10f02: Pulling fs layer m-k8s-1.20: c6568d217a00: Verifying Checksum m-k8s-1.20: c6568d217a00: Download complete m-k8s-1.20: c6568d217a00: Pull complete m-k8s-1.20: 6937ebe10f02: Verifying Checksum m-k8s-1.20: filesystem layer verification failed for digest sha256:6937ebe10f0225ac2ef529a733a02d46829421411fb9e33145f19d4026d75478 m-k8s-1.20: , error: exit status 1 m-k8s-1.20: [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` m-k8s-1.20: To see the stack trace of this error execute with --v=5 or higher
VirtualBox 와 vagrant 를 강의와 동일한 버전으로 재설치하고
vagrant destory / vagrant up 을 실행하는 등을 시도해보았으나 동일한 에러가 발생하였습니다.
원인을 확인하기가 어려워 혹시 해결방안이 있는지 알고 싶습니다