Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Host-only adapters are no longer supported by Virtualbox #88

Open
torfinnberset opened this issue Nov 12, 2022 · 1 comment
Open

Host-only adapters are no longer supported by Virtualbox #88

torfinnberset opened this issue Nov 12, 2022 · 1 comment

Comments

@torfinnberset
Copy link

Host: Intel macOS 12.6
VirtualBox: 7.0.2

~/github/windows-docker-machine  main $ vagrant up --provider virtualbox 2022-box 

Bringing machine '2022-box' up with 'virtualbox' provider...
==> 2022-box: Box 'StefanScherer/windows_2022_docker' could not be found. Attempting to find and install...
    2022-box: Box Provider: virtualbox
    2022-box: Box Version: >= 0
==> 2022-box: Loading metadata for box 'StefanScherer/windows_2022_docker'
    2022-box: URL: https://vagrantcloud.com/StefanScherer/windows_2022_docker
==> 2022-box: Adding box 'StefanScherer/windows_2022_docker' (v2022.06.10) for provider: virtualbox
    2022-box: Downloading: https://vagrantcloud.com/StefanScherer/boxes/windows_2022_docker/versions/2022.06.10/providers/virtualbox.box
    2022-box: Calculating and comparing box checksum...
==> 2022-box: Successfully added box 'StefanScherer/windows_2022_docker' (v2022.06.10) for 'virtualbox'!
==> 2022-box: Preparing master VM for linked clones...
    2022-box: This is a one time operation. Once the master VM is prepared,
    2022-box: it will be used as a base for linked clones, making the creation
    2022-box: of new VMs take milliseconds on a modern system.
==> 2022-box: Importing base box 'StefanScherer/windows_2022_docker'...
==> 2022-box: Cloning VM...
==> 2022-box: Matching MAC address for NAT networking...
==> 2022-box: Checking if box 'StefanScherer/windows_2022_docker' version '2022.06.10' is up to date...
==> 2022-box: Setting the name of the VM: windows-docker-machine_2022-box_1668244837824_50438
==> 2022-box: Clearing any previously set network interfaces...
==> 2022-box: Preparing network interfaces based on configuration...
    2022-box: Adapter 1: nat
    2022-box: Adapter 2: hostonly
==> 2022-box: Forwarding ports...
    2022-box: 3389 (guest) => 3389 (host) (adapter 1)
    2022-box: 5985 (guest) => 55985 (host) (adapter 1)
    2022-box: 5986 (guest) => 55986 (host) (adapter 1)
    2022-box: 22 (guest) => 2222 (host) (adapter 1)
==> 2022-box: Running 'pre-boot' VM customizations...
==> 2022-box: 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", "afc941eb-c0d5-4433-8f68-227b9b571d65", "--type", "headless"]

Stderr: VBoxManage: error: Host-only adapters are no longer supported!
VBoxManage: error: For your convenience a host-only network named 'Legacy vboxnet1 Network' has been created with network mask '255.255.255.0' and IP address range '192.168.59.1' - '192.168.59.254'.
VBoxManage: error: To fix this problem, switch to 'Host-only Network' attachment type in the VM settings.
VBoxManage: error:  (VERR_NOT_FOUND)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Changing to "Host-only network" via the VirtualBox UI does not resolve the issue, as the command above reconfigures it back to the deprecated adapter.

@gabyx
Copy link

gabyx commented Jan 22, 2023

This issues seems resolved, as this worked for me:

macOS BigSur and Virtuabox 7.0.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants