인프런 커뮤니티 질문&답변
작성한 질문수
2.4.베이그런트(Vagrant)+버추얼박스/vagrant up issue
작성
·
39
·
수정됨
0
m2 air 씁니다
2.4 폴더 이하 .cmd 명령어로 brew install 완료했습니다
아래 명령어에 대해 이슈가 게속 생깁니다
tabby,virtualbox ... 다 지우고 새로해봐도 같은 이슈입니다
gpt에게 물어보며 끙끙대며 하고있습니다
도와주세요
insuchoe@InSooAir 2.4 % brew install --cask ./virtualbox-v7.1.10/virtualbox.rb
==> Auto-updating Homebrew...
Adjust how often this is run with HOMEBREW_AUTO_UPDATE_SECS or disable with
HOMEBREW_NO_AUTO_UPDATE. Hide these hints with HOMEBREW_NO_ENV_HINTS (see man brew).
==> Downloading https://download.virtualbox.org/virtualbox/7.1.10/VirtualBox-7.1.10-
Already downloaded: /Users/insuchoe/Library/Caches/Homebrew/downloads/c10847be12cf61160d18b66cf2be3cce1143d8a2b0b1ffc046a0a235892dc4c4--VirtualBox-7.1.10-169112-macOSArm64.dmg
==> Installing Cask virtualbox
==> Running installer for virtualbox with sudo; the password may be necessary.
Password:
installer: Package name is Oracle VirtualBox
installer: choices changes file '/private/tmp/choices20250730-26606-y3yqd9.xml' applied
installer: Installing at base path /
installer: The install was successful.
🍺 virtualbox was successfully installed!
==> No outdated dependents to upgrade!
insuchoe@InSooAir 2.4 % brew install --cask ./vagrant-v2.4.7/vagrant.rb
==> Downloading https://releases.hashicorp.com/vagrant/2.4.7/vagrant_2.4.7_darwin_ar
Already downloaded: /Users/insuchoe/Library/Caches/Homebrew/downloads/3d87ee0b909cfd886c1232aa833f37c3beeba1dabd0fa72292af0d74c896123d--vagrant_2.4.7_darwin_arm64.dmg
==> Installing Cask vagrant
==> Running installer for vagrant with sudo; the password may be necessary.
Password:
installer: Package name is Vagrant
installer: Upgrading at base path /
installer: The upgrade was successful.
==> Linking Bash Completion 'completion.sh' to '/opt/homebrew/etc/bash_completion.d/
==> Linking Zsh Completion '_vagrant' to '/opt/homebrew/share/zsh/site-functions/_va
🍺 vagrant was successfully installed!
==> No outdated dependents to upgrade!
insuchoe@InSooAir 2.4 %
insuchoe@InSooAir 2.4 % brew install --cask ./tabby-v1.0.207/tabby.rb
==> Downloading https://github.com/Eugeny/tabby/releases/download/v1.0.207/tabby-1.0
Already downloaded: /Users/insuchoe/Library/Caches/Homebrew/downloads/6ac0899dd17d84fb668f23226094b674bf7f5615155b29ba53a109c4d519e782--tabby-1.0.207-macos-arm64.zip
==> Installing Cask tabby
==> Moving App 'Tabby.app' to '/Applications/Tabby.app'
🍺 tabby was successfully installed!
==> No outdated dependents to upgrade!
cp ./tabby-v1.0.207/config.yaml ~/Library/Application\ Support/tabby/ -- 맨마지막으로 입력함
insuchoe@InSooAir 2.4 % vagrant up
Bringing machine 'cp-k8s-1.30.3' up with 'virtualbox' provider...
Bringing machine 'w1-k8s-1.30.3' up with 'virtualbox' provider...
Bringing machine 'w2-k8s-1.30.3' up with 'virtualbox' provider...
Bringing machine 'w3-k8s-1.30.3' up with 'virtualbox' provider...
==> cp-k8s-1.30.3: Importing base box 'sysnet4admin/Ubuntu-k8s'...
==> cp-k8s-1.30.3: Matching MAC address for NAT networking...
==> cp-k8s-1.30.3: Checking if box 'sysnet4admin/Ubuntu-k8s' version '0.8.6' is up to date...
==> cp-k8s-1.30.3: Setting the name of the VM: cp-k8s-1.30.3(github_SysNet4Admin)
==> cp-k8s-1.30.3: Clearing any previously set network interfaces...
The specified host network collides with a non-hostonly network!
This will cause your specified IP to be inaccessible. Please change
the IP or name of your host only network so that it no longer matches that of
a bridged or non-hostonly network.
Bridged Network Address: '192.168.1.0'
Host-only Network 'bridge102': '192.168.1.0'
insuchoe@InSooAir 2.4 %
답변 2
0
답변2번 방법 채택
https://github.com/sysnet4admin/IaC/tree/master/k8s/C
insuchoe@InSooAir vagrant_projects % git clone https://github.com/sysnet4admin/IaC.git
'IaC'에 복제합니다...
remote: Enumerating objects: 4523, done.
remote: Counting objects: 100% (866/866), done.
remote: Compressing objects: 100% (703/703), done.
remote: Total 4523 (delta 158), reused 847 (delta 151), pack-reused 3657 (from 2)
오브젝트를 받는 중: 100% (4523/4523), 19.08 MiB | 10.85 MiB/s, 완료.
델타를 알아내는 중: 100% (2147/2147), 완료.
insuchoe@InSooAir vagrant_projects % cd IaC/k8s/C/k8s-min-1.16.15-iprange16
insuchoe@InSooAir k8s-min-1.16.15-iprange16 % vagrant up
Bringing machine 'm-k8s-1.16' up with 'virtualbox' provider...
Bringing machine 'w1-k8s-1.16' up with 'virtualbox' provider...
Bringing machine 'w2-k8s-1.16' up with 'virtualbox' provider...
Bringing machine 'w3-k8s-1.16' up with 'virtualbox' provider...
==> m-k8s-1.16: Box 'sysnet4admin/CentOS-k8s' could not be found. Attempting to find and install...
m-k8s-1.16: Box Provider: virtualbox
m-k8s-1.16: Box Version: >= 0
==> m-k8s-1.16: Loading metadata for box 'sysnet4admin/CentOS-k8s'
m-k8s-1.16: URL: https://vagrantcloud.com/api/v2/vagrant/sysnet4admin/CentOS-k8s
==> m-k8s-1.16: Adding box 'sysnet4admin/CentOS-k8s' (v0.8.0) for provider: virtualbox
m-k8s-1.16: Downloading: https://vagrantcloud.com/sysnet4admin/boxes/CentOS-k8s/versions/0.8.0/providers/virtualbox/unknown/vagrant.box
==> m-k8s-1.16: Successfully added box 'sysnet4admin/CentOS-k8s' (v0.8.0) for 'virtualbox'!
==> m-k8s-1.16: Importing base box 'sysnet4admin/CentOS-k8s'...
==> m-k8s-1.16: Matching MAC address for NAT networking...
==> m-k8s-1.16: Checking if box 'sysnet4admin/CentOS-k8s' version '0.8.0' is up to date...
==> m-k8s-1.16: Setting the name of the VM: m-k8s-1.16(github_SysNet4Admin)
==> m-k8s-1.16: Clearing any previously set network interfaces...
==> m-k8s-1.16: Preparing network interfaces based on configuration...
m-k8s-1.16: Adapter 1: nat
m-k8s-1.16: Adapter 2: hostonly
==> m-k8s-1.16: Forwarding ports...
m-k8s-1.16: 22 (guest) => 61610 (host) (adapter 1)
==> m-k8s-1.16: Running 'pre-boot' VM customizations...
==> m-k8s-1.16: Booting VM...
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "aa094247-7e57-4098-a145-272481ab9353", "--type", "headless"]
Stderr: VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession
여전히 이슈가 있습니다
도와주세요
% ipconfig getifaddr en0
110.35.191.78
지피티에게 물어봐가며 진행중입니다
공인 아이피대역으로 베이그런파일의 노드들을 바꾸려고 하니
안된다고 하네요 위험하다고 하지마라고 답변을 지피티에게 받아서
다음 솔루션 찾아보면서 물어보면서 진행중입니다
Vagrant 파일은 백업해두었고 다음과같이 수정해서 "vagrant up" 다시 시작했습니다
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
Started all configured services on all networks
DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is disabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is disabled
Some/All of the configured services are not running
insuchoe@InSooAir scripts % cat vf_net_reset.sh
#!/usr/bin/env bash
# Reset VMware Fusion Networking
# Clear out the Configuration
sudo rm -f /Library/Preferences/VMware\ Fusion/networking*
sudo rm -f /Library/Preferences/VMware\ Fusion/*location*
sudo rm -rf /Library/Preferences/VMware\ Fusion/vmnet*
sudo rm -rf /var/db/vmware/vmnet-dhcpd-vmnet*
# Reconfigure Networking
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli -c
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --status
insuchoe@InSooAir scripts % clear
insuchoe@InSooAir scripts % ls
vfnet_create_vnet2.sh vf_net_create_vnet2.sh
copy_launchctl-all-vmware-utility.sh vf_net_reset.sh
copy_netstat-anvp.sh
insuchoe@InSooAir scripts % sudo sh copy_launchctl-all-vmware-utility.sh
insuchoe@InSooAir scripts % sudo sh copy_netstat-anvp.sh
insuchoe@InSooAir scripts % sudo sh vf_net_create_vnet2.sh
Library Loaded
vmnetcfg: vnlvnetcfgadd - successfully added key:value - VNET_7_DHCP:no
Library Loaded
vmnetcfg: vnlvnetcfgadd - successfully added key:value - VNET_7_HOSTONLY_SUBNET:192.168.250.0
Library Loaded
vmnetcfg: vnlvnetcfgadd - successfully added key:value - VNET_7_HOSTONLY_NETMASK:255.255.255.0
Library Loaded
vmnetcfg: vnlvnetcfgadd - successfully added key:value - VNET_7_NAT:yes
Library Loaded
vmnetcfg: vnlvnetcfgadd - successfully added key:value - VNET_7_VIRTUAL_ADAPTER:yes
Stopped DHCP service on vmnet1
Stopped DHCP service on vmnet8
Started all configured services on all networks
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
insuchoe@InSooAir scripts % cat vf_net_reset.sh
sudo rm -f /Library/Preferences/VMware\ Fusion/*location*
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start
Library Loaded
Library Loaded
Stopped NAT service on vmnet8
Vagrant.configure("2") do |config|
# -*- mode: ruby -*-
Stopped all configured services on all networks
Backed up existing network settings to backup file "/tmp/vmware.pbsqK7"
Restored network settings
Stopped all configured services on all networks
Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Started NAT service on vmnet7
Enabled hostonly virtual adapter on vmnet7
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
Started all configured services on all networks
insuchoe@InSooAir scripts % cd ..
insuchoe@InSooAir 2.4 % ls
k8s-adv vagrant-v2.4.1
scripts vagrant-vmware-utility-1.0.22
tabby-v1.0.207 vmware-fusion-v13.5.2
insuchoe@InSooAir 2.4 % cd k8s-adv
insuchoe@InSooAir k8s-adv % ls
Vagrantfile extra_k8s_pkgs.sh worker_nodes.sh
Vagrantfile k8senv_build.sh
controlplane_node.sh k8s_pkg_cfg.sh
insuchoe@InSooAir k8s-adv % vi Vagrantfile
insuchoe@InSooAir k8s-adv % vim Vagrantfile
insuchoe@InSooAir k8s-adv % vim Vagrantfile
insuchoe@InSooAir k8s-adv % vagrant up
Bringing machine 'cp-k8s-1.30.1' up with 'vmware_desktop' provider...
Bringing machine 'worker1' up with 'vmware_desktop' provider...
Bringing machine 'worker2' up with 'vmware_desktop' provider...
Bringing machine 'worker3' up with 'vmware_desktop' provider...
==> cp-k8s-1.30.1: Checking if box 'sysnet4admin/Ubuntu-k8s' version '0.8.6' is up to date...
==> cp-k8s-1.30.1: Verifying vmnet devices are healthy...
==> cp-k8s-1.30.1: Preparing network adapters...
==> cp-k8s-1.30.1: Starting the VMware VM...
==> cp-k8s-1.30.1: Waiting for the VM to receive an address...
==> cp-k8s-1.30.1: Forwarding ports...
cp-k8s-1.30.1: -- 22 => 2222
==> cp-k8s-1.30.1: Waiting for machine to boot. This may take a few minutes...
cp-k8s-1.30.1: SSH address: 127.0.0.1:2222
cp-k8s-1.30.1: SSH username: vagrant
cp-k8s-1.30.1: SSH auth method: private key
cp-k8s-1.30.1:
cp-k8s-1.30.1: Vagrant insecure key detected. Vagrant will automatically replace
cp-k8s-1.30.1: this with a newly generated keypair for better security.
cp-k8s-1.30.1:
cp-k8s-1.30.1: Inserting generated public key within guest...
cp-k8s-1.30.1: Removing insecure key from the guest if it's present...
cp-k8s-1.30.1: Key inserted! Disconnecting and reconnecting using new SSH key...
==> cp-k8s-1.30.1: Machine booted and ready!
==> cp-k8s-1.30.1: Setting hostname...
==> cp-k8s-1.30.1: Configuring network adapters within the VM...
==> cp-k8s-1.30.1: Waiting for HGFS to become available...
==> cp-k8s-1.30.1: Enabling and configuring shared folders...
cp-k8s-1.30.1: -- /Users/insuchoe/Desktop/edu/k8s_edu_learning/.archived/2.4/k8s-adv: /vagrant
==> worker1: Cloning VMware VM: 'sysnet4admin/Ubuntu-k8s'. This can take some time...
==> worker1: Checking if box 'sysnet4admin/Ubuntu-k8s' version '0.8.6' is up to date...
==> worker1: Verifying vmnet devices are healthy...
==> worker1: Preparing network adapters...
==> worker1: Fixed port collision for 22 => 2222. Now on port 2200.
==> worker1: Starting the VMware VM...
==> worker1: Waiting for the VM to receive an address...
==> worker1: Forwarding ports...
worker1: -- 22 => 2200
==> worker1: Waiting for machine to boot. This may take a few minutes...
worker1: SSH address: 127.0.0.1:2200
worker1: SSH username: vagrant
worker1: SSH auth method: private key
worker1:
worker1: Vagrant insecure key detected. Vagrant will automatically replace
worker1: this with a newly generated keypair for better security.
worker1:
worker1: Inserting generated public key within guest...
worker1: Removing insecure key from the guest if it's present...
worker1: Key inserted! Disconnecting and reconnecting using new SSH key...
==> worker1: Machine booted and ready!
==> worker1: Setting hostname...
==> worker1: Configuring network adapters within the VM...
==> worker1: Waiting for HGFS to become available...
==> worker1: Enabling and configuring shared folders...
worker1: -- /Users/insuchoe/Desktop/edu/k8s_edu_learning/.archived/2.4/k8s-adv: /vagrant
==> worker2: Cloning VMware VM: 'sysnet4admin/Ubuntu-k8s'. This can take some time...
==> worker2: Checking if box 'sysnet4admin/Ubuntu-k8s' version '0.8.6' is up to date...
==> worker2: Verifying vmnet devices are healthy...
==> worker2: Preparing network adapters...
==> worker2: Fixed port collision for 22 => 2222. Now on port 2201.
==> worker2: Starting the VMware VM...
==> worker2: Waiting for the VM to receive an address...
==> worker2: Forwarding ports...
worker2: -- 22 => 2201
==> worker2: Waiting for machine to boot. This may take a few minutes...
worker2: SSH address: 127.0.0.1:2201
worker2: SSH username: vagrant
worker2: SSH auth method: private key
worker2:
worker2: Vagrant insecure key detected. Vagrant will automatically replace
worker2: this with a newly generated keypair for better security.
worker2:
worker2: Inserting generated public key within guest...
worker2: Removing insecure key from the guest if it's present...
worker2: Key inserted! Disconnecting and reconnecting using new SSH key...
==> worker2: Machine booted and ready!
==> worker2: Setting hostname...
==> worker2: Configuring network adapters within the VM...
==> worker2: Waiting for HGFS to become available...
==> worker2: Enabling and configuring shared folders...
worker2: -- /Users/insuchoe/Desktop/edu/k8s_edu_learning/.archived/2.4/k8s-adv: /vagrant
==> worker3: Cloning VMware VM: 'sysnet4admin/Ubuntu-k8s'. This can take some time...
==> worker3: Checking if box 'sysnet4admin/Ubuntu-k8s' version '0.8.6' is up to date...
==> worker3: Verifying vmnet devices are healthy...
==> worker3: Preparing network adapters...
==> worker3: Fixed port collision for 22 => 2222. Now on port 2202.
==> worker3: Starting the VMware VM...
==> worker3: Waiting for the VM to receive an address...
==> worker3: Forwarding ports...
worker3: -- 22 => 2202
==> worker3: Waiting for machine to boot. This may take a few minutes...
worker3: SSH address: 127.0.0.1:2202
worker3: SSH username: vagrant
worker3: SSH auth method: private key
worker3:
worker3: Vagrant insecure key detected. Vagrant will automatically replace
worker3: this with a newly generated keypair for better security.
worker3:
worker3: Inserting generated public key within guest...
worker3: Removing insecure key from the guest if it's present...
worker3: Key inserted! Disconnecting and reconnecting using new SSH key...
==> worker3: Machine booted and ready!
==> worker3: Setting hostname...
==> worker3: Configuring network adapters within the VM...
==> worker3: Waiting for HGFS to become available...
==> worker3: Enabling and configuring shared folders...
worker3: -- /Users/insuchoe/Desktop/edu/k8s_edu_learning/.archived/2.4/k8s-adv: /vagrant
insuchoe@InSooAir k8s-adv % vagrant ssh cp-k8s-1.30.1
Welcome to Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-124-generic aarch64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Fri Aug 1 10:43:25 PM KST 2025
System load: 0.12 Processes: 245
Usage of /: 13.0% of 29.82GB Users logged in: 0
Memory usage: 11% IPv4 address for eth0: 192.168.93.128
Swap usage: 0%
This system is built by the Bento project by Chef Software
More information can be found at https://github.com/chef/bento
vagrant@cp-k8s:~$ exit
logout
insuchoe@InSooAir k8s-adv % vagrant ssh worker1
Welcome to Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-124-generic aarch64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Fri Aug 1 10:43:39 PM KST 2025
System load: 0.03 Processes: 244
Usage of /: 13.2% of 29.82GB Users logged in: 0
Memory usage: 11% IPv4 address for eth0: 192.168.93.129
Swap usage: 0%
This system is built by the Bento project by Chef Software
More information can be found at https://github.com/chef/bento
vagrant@worker1:~$ exit
logout
insuchoe@InSooAir k8s-adv % vagrant ssh worker2
Welcome to Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-124-generic aarch64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Sat Aug 2 07:41:15 AM KST 2025
System load: 0.6 Processes: 233
Usage of /: 12.7% of 29.82GB Users logged in: 0
Memory usage: 10% IPv4 address for eth0: 192.168.93.130
Swap usage: 0%
# -*- mode: ruby -*-
# vi: set ft=ruby :
## configuration variables ##
N = 3 # 워커 노드 수
k8s_V = '1.30.1-1.1' # Kubernetes 버전
ctrd_V = '1.6.28-1' # Containerd 버전
controller_IP = '192.168.250.10' # 컨트롤 플레인 IP (vmnet7 대역)
Vagrant.configure("2") do |config|
#====================#
# Control-Plane Node #
#====================#
config.vm.define "cp-k8s-#{k8s_V[0..5]}" do |cfg|
cfg.vm.box = "sysnet4admin/Ubuntu-k8s"
cfg.vm.hostname = "cp-k8s"
cfg.vm.network "private_network", ip: controller_IP
cfg.vm.provider "vmware_desktop" do |vb|
This system is built by the Bento project by Chef Software
# -*- mode: ruby -*-
# vi: set ft=ruby :
## configuration variables ##
N = 3 # 워커 노드 수
k8s_V = '1.30.1-1.1' # Kubernetes 버전
ctrd_V = '1.6.28-1' # Containerd 버전
controller_IP = '192.168.250.10' # 컨트롤 플레인 IP (vmnet7 대역)
Vagrant.configure("2") do |config|
#====================#
# Control-Plane Node #
#====================#
config.vm.define "cp-k8s-#{k8s_V[0..5]}" do |cfg|
cfg.vm.box = "sysnet4admin/Ubuntu-k8s"
cfg.vm.hostname = "cp-k8s"
cfg.vm.network "private_network", ip: controller_IP
cfg.vm.provider "vmware_desktop" do |vb|
vb.gui = false
vb.cpus = 2
vb.memory = 2048
end
end
"Vagrantfile" 45L, 1178B
"vagrant up" 실행전 기존의 스크립트 구성의 vf_net_create_vnet2.sh 를 변경해주었습니다. 물론 백업을 하고 진행했습니다.
...생략
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_7_HOSTONLY_SUBNET 192.168.250.0
...생략
"vagrant up" 명령 하달 후
다음 명령어로 접속을 시도 해봤는데 문제는 없는 상황입니다
vagrant ssh cp-k8s-1.30.1
vagrant ssh worker1
vagrant ssh worker2
vagrant ssh worker3
음....현재는 VMware Fusion은 추천하지 않고 있는 상황이긴 한데...
일단 사용 가능하시니 그걸로 사용하셔도 괜찮을 것 같습니다.
VMware Fusion 사용 시에 VM 전원 종료를 하게 되면 vagrant로 설정된 포트포워딩이 동작하지 않으니 해당 부분만 참고하세요.
(즉, 일시 정지 || , suspend로만 해두고 사용하셔야 합니다.)
0
안녕하세요, 인프런 AI 인턴입니다.
현재 발생한 오류는 Vagrant가 MacOS에서 가상 머신을 설정할 때 네트워크 주소가 겹치는 경우에 발생하는 것으로 보입니다. Vagrant는 종종 사용자의 네트워크 설정과 충돌할 수 있는 IP를 자동으로 할당하려고 하며, 현재 충돌이 발생하고 있습니다. 이 문제를 해결하기 위해선 Vagrant의 설정 파일에서 네트워크 IP 주소를 변경하는 것이 필요합니다.
비슷한 문제를 겪으셨던 분들의 게시물 및 해결 방법입니다:
1.2 vagrant up 명령 수행시 에러 - 이는 Vagrant에서 네트워크 설정 문제가 발생했을 때의 일반적인 해결 방법을 설명합니다. 네트워크 주소를 변경하거나 기존 네트워크 설정을 수동으로 조정하여 충돌을 피하는 방법을 제안하고 있습니다.
vagrant up 실행 시 문제 발생 - VirtualBox 사용자라면, 호스트 전용 네트워크 설정을 수동으로 변경하여 IP 충돌을 피해야 할 수도 있습니다.
vagrant up 시 오류 - 네트워크 설정 외에도 환경의 충돌 문제를 해결하는 방법을 소개합니다.
위 링크들의 해결책을 참고하여, 다음과 같은 방법으로 시도해 보세요:
- Vagrantfile을 열어서 가상 머신에 할당된 IP를 192.168.56.x와 같은 다른 서브넷으로 변경합니다.
- 또는 VirtualBox 네트워크 설정에서 현재의 호스트-온리 네트워크 구성을 삭제하거나 수정하여 충돌을 해결합니다.
이로써 문제를 해결하실 수 있기를 바랍니다. 설명이 충분하지 않거나 더 궁금한 점이 있다면 추가적으로 질문해 주세요. 지식공유자가 자세히 도와줄 것입니다.
저는 질문자님의 이해를 돕고자 지식공유자님의 기존 답변을 참고하여 유사한 답변 링크를 추천해드리고 있습니다. 현재 베타 기능으로 답변이 만족스럽지 않을 수 있는 점 양해 부탁드립니다. 🙏 추가적으로 궁금한 점이 있으시면, 이어서 질문해 주세요. 곧 지식공유자께서 답변해 주실 것입니다.
저 당시의 버전은 지금 실습으로 하기에는 좀 부족함이 많을 것 같고요.
따라서 저거 말고 현재 진행하시는 소스의 내용에 IP를 수정하여 진행 가능할 수도 있긴 한데 복잡하실꺼라..
제 생각에는 현재 홈 네트워크 (또는 할리스?) 의 네트워크 대역을 겹치지 않도록 바꾸시는게 어떨까 싶습니다.
혹시 홈네트워크의 설정이 192.168.1.0/24 가 아니라면 말씀 부탁드려요.
맥OS면 아마 ipconfig 로 보시면 현재 사용하는 네트워크 아실 수 있을껍니다.
현재 실습에는 192.168.1.0/24 대역이 필요합니다.