Vagrant up 에러 발생 문제 해결 도움 요청

Question

1.5버전 실습환경 구축을 위해

Virtual box와 vagrant 설치 후 공유해 주신 1.5버전 설치 중 에러가 계속 발생하여 Virtualbox와 vagrant를 재설치 해 보았으나, 여전히 동일한 문제가 발생합니다.

혹시 문제 해결에 도움을 주실 수 있을지 문의 드립니다.

문제된 화면 캡쳐 올려 드립니다.

Microsoft Windows [Version 10.0.18362.1256] (c) 2019 Microsoft Corporation. All rights reserved. C:\Users\Administrator>cd \ C:\>cd hashicorp C:\HashiCorp>dir/w C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp 디렉터리 [.] [..] [Vagrant] [_Lecture_k8s_learning.kit-main] _Lecture_k8s_learning.kit-main.zip 1개 파일 438,711 바이트 4개 디렉터리 66,036,817,920 바이트 남음 C:\HashiCorp>cd _Lecture_k8s_learning.kit-main C:\HashiCorp\_Lecture_k8s_learning.kit-main>dir C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp\_Lecture_k8s_learning.kit-main 디렉터리 2021-10-06 오후 01:48 <DIR> . 2021-10-06 오후 01:48 <DIR> .. 2021-10-05 오전 01:00 9 .gitignore 2021-10-06 오후 01:46 <DIR> A 2021-10-06 오후 01:46 <DIR> ch1 2021-10-06 오후 01:46 <DIR> ch2 2021-10-06 오후 01:46 <DIR> ch3 2021-10-06 오후 01:46 <DIR> ch4 2021-10-06 오후 01:46 <DIR> ch5 2021-10-06 오후 01:46 <DIR> ch6 2021-10-06 오후 01:46 <DIR> ch7 2021-10-06 오후 01:46 <DIR> ch8 2021-10-06 오후 01:46 <DIR> ch9 2021-10-05 오전 01:00 1,472 README.md 2개 파일 1,481 바이트 12개 디렉터리 66,036,817,920 바이트 남음 C:\HashiCorp\_Lecture_k8s_learning.kit-main>cd ch1 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1>dir C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1 디렉터리 2021-10-06 오후 01:46 <DIR> . 2021-10-06 오후 01:46 <DIR> .. 2021-10-06 오후 01:46 <DIR> 1.5 2021-10-06 오후 01:46 <DIR> 1.6 2021-10-05 오전 01:00 182 README.md 1개 파일 182 바이트 4개 디렉터리 66,036,817,920 바이트 남음 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1>cd 1.5 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5>dir/w C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5 디렉터리 [.] [..] [k8s-min-5GiB-wo-add-nodes] Sessions(k8s_learning).XML 1개 파일 1,373 바이트 3개 디렉터리 66,036,822,016 바이트 남음 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5>cd k8s-min-5GiB-wo-add-nodes C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes>dir C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes 디렉터리 2021-10-06 오후 01:46 <DIR> . 2021-10-06 오후 01:46 <DIR> .. 2021-10-05 오전 01:00 1,395 k8s_env_build.sh 2021-10-05 오전 01:00 475 k8s_pkg_cfg.sh 2021-10-05 오전 01:00 524 k_cfg_n_git_clone.sh 2021-10-05 오전 01:00 2,275 Vagrantfile 4개 파일 4,669 바이트 2개 디렉터리 66,036,707,328 바이트 남음 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes>dir/w C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes 디렉터리 [.] [..] k8s_env_build.sh k8s_pkg_cfg.sh k_cfg_n_git_clone.sh Vagrantfile 4개 파일 4,669 바이트 2개 디렉터리 66,036,707,328 바이트 남음 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes>vagrant up Bringing machine 'WO-m-k8s-1.20' up with 'virtualbox' provider... Bringing machine 'WO-w1-k8s-1.20' up with 'virtualbox' provider... Bringing machine 'WO-w2-k8s-1.20' up with 'virtualbox' provider... Bringing machine 'WO-w3-k8s-1.20' up with 'virtualbox' provider... ==> WO-m-k8s-1.20: Box 'sysnet4admin/CentOS-k8s' could not be found. Attempting to find and install... WO-m-k8s-1.20: Box Provider: virtualbox WO-m-k8s-1.20: Box Version: >= 0 ==> WO-m-k8s-1.20: Loading metadata for box 'sysnet4admin/CentOS-k8s' WO-m-k8s-1.20: URL: https://vagrantcloud.com/sysnet4admin/CentOS-k8s ==> WO-m-k8s-1.20: Adding box 'sysnet4admin/CentOS-k8s' (v0.7.4) for provider: virtualbox WO-m-k8s-1.20: Downloading: https://vagrantcloud.com/sysnet4admin/boxes/CentOS-k8s/versions/0.7.4/providers/virtualbox.box WO-m-k8s-1.20: ==> WO-m-k8s-1.20: Successfully added box 'sysnet4admin/CentOS-k8s' (v0.7.4) for 'virtualbox'! ==> WO-m-k8s-1.20: Importing base box 'sysnet4admin/CentOS-k8s'... ==> WO-m-k8s-1.20: Matching MAC address for NAT networking... ==> WO-m-k8s-1.20: Checking if box 'sysnet4admin/CentOS-k8s' version '0.7.4' is up to date... ==> WO-m-k8s-1.20: Setting the name of the VM: WO-m-k8s-1.20(github_SysNet4Admin) ==> WO-m-k8s-1.20: Clearing any previously set network interfaces... ==> WO-m-k8s-1.20: Preparing network interfaces based on configuration... WO-m-k8s-1.20: Adapter 1: nat WO-m-k8s-1.20: Adapter 2: hostonly ==> WO-m-k8s-1.20: Forwarding ports... WO-m-k8s-1.20: 22 (guest) => 60010 (host) (adapter 1) ==> WO-m-k8s-1.20: Running 'pre-boot' VM customizations... ==> WO-m-k8s-1.20: Booting VM... ==> WO-m-k8s-1.20: Waiting for machine to boot. This may take a few minutes... WO-m-k8s-1.20: SSH address: 127.0.0.1:60010 WO-m-k8s-1.20: SSH username: vagrant WO-m-k8s-1.20: SSH auth method: private key WO-m-k8s-1.20: Warning: Remote connection disconnect. Retrying... WO-m-k8s-1.20: Warning: Connection aborted. Retrying... WO-m-k8s-1.20: Warning: Remote connection disconnect. Retrying... WO-m-k8s-1.20: Warning: Remote connection disconnect. Retrying... WO-m-k8s-1.20: Warning: Connection aborted. Retrying... WO-m-k8s-1.20: WO-m-k8s-1.20: Vagrant insecure key detected. Vagrant will automatically replace WO-m-k8s-1.20: this with a newly generated keypair for better security. WO-m-k8s-1.20: WO-m-k8s-1.20: Inserting generated public key within guest... WO-m-k8s-1.20: Removing insecure key from the guest if it's present... WO-m-k8s-1.20: Key inserted! Disconnecting and reconnecting using new SSH key... ==> WO-m-k8s-1.20: Machine booted and ready! ==> WO-m-k8s-1.20: Checking for guest additions in VM... ==> WO-m-k8s-1.20: Setting hostname... ==> WO-m-k8s-1.20: Configuring and enabling network interfaces... ==> WO-m-k8s-1.20: Running provisioner: shell... WO-m-k8s-1.20: Running: C:/Users/ADMINI~1/AppData/Local/Temp/vagrant-shell20211006-15576-1w8qnwz.sh WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Determining fastest mirrors WO-m-k8s-1.20: * base: mirror.kakao.com WO-m-k8s-1.20: * extras: mirror.kakao.com WO-m-k8s-1.20: * updates: mirror.kakao.com WO-m-k8s-1.20: Package yum-utils-1.1.31-54.el7_8.noarch already installed and latest version WO-m-k8s-1.20: Nothing to do WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: adding repo from: https://download.docker.com/linux/centos/docker-ce.repo WO-m-k8s-1.20: grabbing file https://download.docker.com/linux/centos/docker-ce.repo to /etc/yum.repos.d/docker-ce.repo WO-m-k8s-1.20: repo saved to /etc/yum.repos.d/docker-ce.repo ==> WO-m-k8s-1.20: Running provisioner: shell... WO-m-k8s-1.20: Running: C:/Users/ADMINI~1/AppData/Local/Temp/vagrant-shell20211006-15576-e5eysz.sh WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Loading mirror speeds from cached hostfile WO-m-k8s-1.20: * base: mirror.kakao.com WO-m-k8s-1.20: * extras: mirror.kakao.com WO-m-k8s-1.20: * updates: mirror.kakao.com WO-m-k8s-1.20: Resolving Dependencies WO-m-k8s-1.20: --> Running transaction check WO-m-k8s-1.20: ---> Package epel-release.noarch 0:7-11 will be installed WO-m-k8s-1.20: --> Finished Dependency Resolution WO-m-k8s-1.20: WO-m-k8s-1.20: Dependencies Resolved WO-m-k8s-1.20: WO-m-k8s-1.20: ================================================================================ WO-m-k8s-1.20: Package Arch Version Repository Size WO-m-k8s-1.20: ================================================================================ WO-m-k8s-1.20: Installing: WO-m-k8s-1.20: epel-release noarch 7-11 extras 15 k WO-m-k8s-1.20: WO-m-k8s-1.20: Transaction Summary WO-m-k8s-1.20: ================================================================================ WO-m-k8s-1.20: Install 1 Package WO-m-k8s-1.20: WO-m-k8s-1.20: Total download size: 15 k WO-m-k8s-1.20: Installed size: 24 k WO-m-k8s-1.20: Downloading packages: WO-m-k8s-1.20: Running transaction check WO-m-k8s-1.20: Running transaction test WO-m-k8s-1.20: Transaction test succeeded WO-m-k8s-1.20: Running transaction WO-m-k8s-1.20: Installing : epel-release-7-11.noarch 1/1 WO-m-k8s-1.20: Verifying : epel-release-7-11.noarch 1/1 WO-m-k8s-1.20: WO-m-k8s-1.20: Installed: WO-m-k8s-1.20: epel-release.noarch 0:7-11 WO-m-k8s-1.20: WO-m-k8s-1.20: Complete! WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Loading mirror speeds from cached hostfile WO-m-k8s-1.20: WO-m-k8s-1.20: WO-m-k8s-1.20: One of the configured repositories failed (Unknown), WO-m-k8s-1.20: and yum doesn't have enough cached data to continue. At this point the only WO-m-k8s-1.20: safe thing yum can do is fail. There are a few ways to work "fix" this: WO-m-k8s-1.20: WO-m-k8s-1.20: 1. Contact the upstream for the repository and get them to fix the problem. WO-m-k8s-1.20: WO-m-k8s-1.20: 2. Reconfigure the baseurl/etc. for the repository, to point to a working WO-m-k8s-1.20: upstream. This is most often useful if you are using a newer WO-m-k8s-1.20: distribution release than is supported by the repository (and the WO-m-k8s-1.20: packages for the previous distribution release still work). WO-m-k8s-1.20: WO-m-k8s-1.20: 3. Run the command with the repository temporarily disabled WO-m-k8s-1.20: yum --disablerepo=<repoid> ... WO-m-k8s-1.20: WO-m-k8s-1.20: 4. Disable the repository permanently, so yum won't use it by default. Yum WO-m-k8s-1.20: will then just ignore the repository until you permanently enable it WO-m-k8s-1.20: again or use --enablerepo for temporary usage: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --disable <repoid> WO-m-k8s-1.20: or WO-m-k8s-1.20: subscription-manager repos --disable=<repoid> WO-m-k8s-1.20: WO-m-k8s-1.20: 5. Configure the failing repository to be skipped, if it is unavailable. WO-m-k8s-1.20: Note that yum will try to contact the repo. when it runs most commands, WO-m-k8s-1.20: so will have to try and fail each time (and thus. yum will be be much WO-m-k8s-1.20: slower). If it is a very temporary problem though, this is often a nice WO-m-k8s-1.20: compromise: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true WO-m-k8s-1.20: WO-m-k8s-1.20: Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Loading mirror speeds from cached hostfile WO-m-k8s-1.20: WO-m-k8s-1.20: WO-m-k8s-1.20: One of the configured repositories failed (Unknown), WO-m-k8s-1.20: and yum doesn't have enough cached data to continue. At this point the only WO-m-k8s-1.20: safe thing yum can do is fail. There are a few ways to work "fix" this: WO-m-k8s-1.20: WO-m-k8s-1.20: 1. Contact the upstream for the repository and get them to fix the problem. WO-m-k8s-1.20: WO-m-k8s-1.20: 2. Reconfigure the baseurl/etc. for the repository, to point to a working WO-m-k8s-1.20: upstream. This is most often useful if you are using a newer WO-m-k8s-1.20: distribution release than is supported by the repository (and the WO-m-k8s-1.20: packages for the previous distribution release still work). WO-m-k8s-1.20: WO-m-k8s-1.20: 3. Run the command with the repository temporarily disabled WO-m-k8s-1.20: yum --disablerepo=<repoid> ... WO-m-k8s-1.20: WO-m-k8s-1.20: 4. Disable the repository permanently, so yum won't use it by default. Yum WO-m-k8s-1.20: will then just ignore the repository until you permanently enable it WO-m-k8s-1.20: again or use --enablerepo for temporary usage: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --disable <repoid> WO-m-k8s-1.20: or WO-m-k8s-1.20: subscription-manager repos --disable=<repoid> WO-m-k8s-1.20: WO-m-k8s-1.20: 5. Configure the failing repository to be skipped, if it is unavailable. WO-m-k8s-1.20: Note that yum will try to contact the repo. when it runs most commands, WO-m-k8s-1.20: so will have to try and fail each time (and thus. yum will be be much WO-m-k8s-1.20: slower). If it is a very temporary problem though, this is often a nice WO-m-k8s-1.20: compromise: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true WO-m-k8s-1.20: WO-m-k8s-1.20: Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Loading mirror speeds from cached hostfile WO-m-k8s-1.20: WO-m-k8s-1.20: WO-m-k8s-1.20: One of the configured repositories failed (Unknown), WO-m-k8s-1.20: and yum doesn't have enough cached data to continue. At this point the only WO-m-k8s-1.20: safe thing yum can do is fail. There are a few ways to work "fix" this: WO-m-k8s-1.20: WO-m-k8s-1.20: 1. Contact the upstream for the repository and get them to fix the problem. WO-m-k8s-1.20: WO-m-k8s-1.20: 2. Reconfigure the baseurl/etc. for the repository, to point to a working WO-m-k8s-1.20: upstream. This is most often useful if you are using a newer WO-m-k8s-1.20: distribution release than is supported by the repository (and the WO-m-k8s-1.20: packages for the previous distribution release still work). WO-m-k8s-1.20: WO-m-k8s-1.20: 3. Run the command with the repository temporarily disabled WO-m-k8s-1.20: yum --disablerepo=<repoid> ... WO-m-k8s-1.20: WO-m-k8s-1.20: 4. Disable the repository permanently, so yum won't use it by default. Yum WO-m-k8s-1.20: will then just ignore the repository until you permanently enable it WO-m-k8s-1.20: again or use --enablerepo for temporary usage: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --disable <repoid> WO-m-k8s-1.20: or WO-m-k8s-1.20: subscription-manager repos --disable=<repoid> WO-m-k8s-1.20: WO-m-k8s-1.20: 5. Configure the failing repository to be skipped, if it is unavailable. WO-m-k8s-1.20: Note that yum will try to contact the repo. when it runs most commands, WO-m-k8s-1.20: so will have to try and fail each time (and thus. yum will be be much WO-m-k8s-1.20: slower). If it is a very temporary problem though, this is often a nice WO-m-k8s-1.20: compromise: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true WO-m-k8s-1.20: WO-m-k8s-1.20: Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Loading mirror speeds from cached hostfile WO-m-k8s-1.20: WO-m-k8s-1.20: WO-m-k8s-1.20: One of the configured repositories failed (Unknown), WO-m-k8s-1.20: and yum doesn't have enough cached data to continue. At this point the only WO-m-k8s-1.20: safe thing yum can do is fail. There are a few ways to work "fix" this: WO-m-k8s-1.20: WO-m-k8s-1.20: 1. Contact the upstream for the repository and get them to fix the problem. WO-m-k8s-1.20: WO-m-k8s-1.20: 2. Reconfigure the baseurl/etc. for the repository, to point to a working WO-m-k8s-1.20: upstream. This is most often useful if you are using a newer WO-m-k8s-1.20: distribution release than is supported by the repository (and the WO-m-k8s-1.20: packages for the previous distribution release still work). WO-m-k8s-1.20: WO-m-k8s-1.20: 3. Run the command with the repository temporarily disabled WO-m-k8s-1.20: yum --disablerepo=<repoid> ... WO-m-k8s-1.20: WO-m-k8s-1.20: 4. Disable the repository permanently, so yum won't use it by default. Yum WO-m-k8s-1.20: will then just ignore the repository until you permanently enable it WO-m-k8s-1.20: again or use --enablerepo for temporary usage: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --disable <repoid> WO-m-k8s-1.20: or WO-m-k8s-1.20: subscription-manager repos --disable=<repoid> WO-m-k8s-1.20: WO-m-k8s-1.20: 5. Configure the failing repository to be skipped, if it is unavailable. WO-m-k8s-1.20: Note that yum will try to contact the repo. when it runs most commands, WO-m-k8s-1.20: so will have to try and fail each time (and thus. yum will be be much WO-m-k8s-1.20: slower). If it is a very temporary problem though, this is often a nice WO-m-k8s-1.20: compromise: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true WO-m-k8s-1.20: WO-m-k8s-1.20: Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again WO-m-k8s-1.20: Failed to execute operation: No such file or directory WO-m-k8s-1.20: Failed to execute operation: No such file or directory The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong. C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes>

* 참고 * 강의에서 다루지 않는 쿠버네티스 범위를 넘는 질문은 쿠버네티스 오픈 채팅 및 유저 그룹을 이용하는게 도움이 될 수 있습니다. (https://open.kakao.com/o/gxSooElb {암호: kubectl}

- 잠깐! 인프런 서비스 운영 관련 문의는 1:1 문의하기를 이용해주세요.

Answer

안녕하세요 설치 진행 중에

gshs  ~/Desktop/kube/_Lecture_k8s_learning.kit-main/ch1/1.5/k8s-min-5GiB-wo-add-nodes  vagrant up  ✔

Bringing machine 'WO-m-k8s-1.20' up with 'virtualbox' provider...

Bringing machine 'WO-w1-k8s-1.20' up with 'virtualbox' provider...

Bringing machine 'WO-w2-k8s-1.20' up with 'virtualbox' provider...

Bringing machine 'WO-w3-k8s-1.20' up with 'virtualbox' provider...

==> WO-m-k8s-1.20: Importing base box 'sysnet4admin/CentOS-k8s'...

==> WO-m-k8s-1.20: Matching MAC address for NAT networking...

==> WO-m-k8s-1.20: Checking if box 'sysnet4admin/CentOS-k8s' version '0.7.4' is up to date...

==> WO-m-k8s-1.20: Setting the name of the VM: WO-m-k8s-1.20(github_SysNet4Admin)

==> WO-m-k8s-1.20: Clearing any previously set network interfaces...

The IP address configured for the host-only network is not within the

allowed ranges. Please update the address used to be within the allowed

ranges and run the command again.

Address: 192.168.1.10

Ranges: 192.168.56.0/21

Valid ranges can be modified in the /etc/vbox/networks.conf file. For

more information including valid format see:

https://www.virtualbox.org/manual/ch06.html#network_hostonly

이런 알림이 나오면서 진행이 안되는데요 어떻게 해야할지 조언 부탁드립니다.

Answer

안녕하세요

위의 내용들이 정확하게 확인은 되지 않지만, 개인 실습 환경과 관련한 요소로 발생한 것으로 보여집니다.

자주 묻는 질문 페이지에 있는 내용을 확인하시고, 조치해 보시고 안되면 다시 문의주실 수 있을까요?

고도

Vagrant up 에러 발생 문제 해결 도움 요청

이 글과 비슷한 Q&A

사이드 프로젝트를 쿠베로 배포하고 싶은데요

ecs fargate service 생성 에러

노드 간에 오토 스케일링 관련 질문

실습환경 구성 관련 문의