-
질문 & 답변
카테고리
-
세부 분야
데브옵스 · 인프라
-
해결 여부
미해결
vagrant up 오류
21.12.23 07:01 작성 조회수 446
1
vagratn up 할 경우
중간중간에 ImagePull 오류가 있는데 이런 경우 timeout으로 봐야하는건가요??
kubeadm config images pull
이부분에서 기다리는 시간이 너무 길었습니다(6시간)
어떤 문제로 오류가 나는지 알고 싶습니다
(다시 설치할경우 또 다시 오랜시간이 걸릴꺼 같아서 문의드림)
-----------------------------------------------------------------------
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.14: output: v1.20.14: Pulling from kube-apiserver
m-k8s-1.20: 0d7d70899875: Pulling fs layer
m-k8s-1.20: d373bafe570e: Pulling fs layer
m-k8s-1.20: 80a294c98ec5: 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: 80a294c98ec5: Verifying Checksum
m-k8s-1.20: filesystem layer verification failed for digest sha256:80a294c98ec5258beb62925658c4781f8a888d320d922fc6df5b8e45e0333f18
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.14: output: v1.20.14: 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: a2a0cc69e98e: Pulling fs layer
m-k8s-1.20: d373bafe570e: Verifying Checksum
m-k8s-1.20: d373bafe570e: Download complete
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: d373bafe570e: Pull complete
m-k8s-1.20: a2a0cc69e98e: Verifying Checksum
m-k8s-1.20: filesystem layer verification failed for digest sha256:a2a0cc69e98eb911834fce5ce36fbc8874cc34ea33a9bea15e5988ffe747dc83
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.14: output: v1.20.14: Pulling from kube-scheduler
m-k8s-1.20: 0d7d70899875: Pulling fs layer
m-k8s-1.20: d373bafe570e: Pulling fs layer
m-k8s-1.20: 0e5b439c245b: 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: 0e5b439c245b: Verifying Checksum
m-k8s-1.20: filesystem layer verification failed for digest sha256:0e5b439c245b02a7f325b5125240ea9b8edb596718d4c0acc9294dc964c27659
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.14: output: v1.20.14: Pulling from kube-proxy
m-k8s-1.20: 20b09fbd3037: Pulling fs layer
m-k8s-1.20: 8931379a3e2d: Pulling fs layer
m-k8s-1.20: 8931379a3e2d: Verifying Checksum
m-k8s-1.20: filesystem layer verification failed for digest sha256:8931379a3e2d97bb0d1cb630b22d2c331acb8282020a0efd07f8de6d5ffcd098
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: 4000adbbc3eb: Pulling fs layer
m-k8s-1.20: d72167780652: Pulling fs layer
m-k8s-1.20: d60490a768b5: Pulling fs layer
m-k8s-1.20: 4a4b5535d134: Pulling fs layer
m-k8s-1.20: 0dac37e8b31a: Pulling fs layer
m-k8s-1.20: 4a4b5535d134: Waiting
m-k8s-1.20: 0dac37e8b31a: Waiting
m-k8s-1.20: 4000adbbc3eb: Verifying Checksum
m-k8s-1.20: 4000adbbc3eb: Download complete
m-k8s-1.20: d72167780652: Verifying Checksum
m-k8s-1.20: 4a4b5535d134: Verifying Checksum
m-k8s-1.20: 4a4b5535d134: Download complete
m-k8s-1.20: 0dac37e8b31a: Verifying Checksum
m-k8s-1.20: filesystem layer verification failed for digest sha256:0dac37e8b31a9abb933416b482b0046f50ec329d35cadfcbf8bcc381fa531114
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: 6937ebe10f02: Verifying Checksum
답변을 작성해보세요.
1
조훈(Hoon Jo)
지식공유자2021.12.23
안녕하세요
시스템에 따라 다르지만 15-30분 넘어가면 정상적으로 보기 어려울 것 같습니다. 위와 같은 image pull 에러가 나신다면, 호스트 시스템의 internet 환경을 체크하셔야 할 것 같습니다.
(예: vpn 또는 해외의 느린망)
0
우주인
질문자2021.12.23
다양한 시도 끝에 해결되었습니다!!!
1. 위에 오류 났던 프로그램 전부 지우기(virtualBox, vagrant 삭제)
2. 강의에 나오는 버전 맞추기
- PC환경
OS : 윈도우10 Pro
CPU : 4Core
램 : 16GB
설치 프로그램 : virtualBox 6.1.18, vagrant2.2.14, vitualboxExtensionPack6.1.18(설치한 이유는
---------------------------------------------------
Stderr: VBoxManage.exe: error: The virtual machine 'm-k8s-1.20(github_SysNet4Admin)' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\dddda\VirtualBox VMs\k8s-SgMST-1.20(github_SysNet4Admin)\m-k8s-1.20(github_SysNet4Admin)\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
--------------------------------------------------
오류로 인해서 인터넷을 찾아보니 설치를 해보라고 해서 설치 했었음, 그리고 Fasoo DRM Client for kybo Book Wix 삭제)
3. VirtualBox 호스트 네트워크에서 DHCP서버 사용함 체크 해제
4. V3 클리닉 서비스 강제종료(백신끄기)
5. 윈도우 방화벽 전부 다 끄기
이렇게 했더니 정상적으로 잘 생성되었습니다
아침에 이른시간인데도 답변 감사합니다
답변 2