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

Windows-10 box fails on macOS #404

Closed
markasbach opened this issue Jul 21, 2023 · 3 comments
Closed

Windows-10 box fails on macOS #404

markasbach opened this issue Jul 21, 2023 · 3 comments
Labels
support Further information is requested

Comments

@markasbach
Copy link

markasbach commented Jul 21, 2023

We've been using the box "gusztavvargadr/windows-10" for some while now (thanks a lot!). Since a few weeks, it seems broken and fails to complete vagrant up with the following messages:

mark@Marks-iMac myproject % vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'gusztavvargadr/windows-10'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'gusztavvargadr/windows-10' version '2202.0.2307' is up to date...
==> default: Setting the name of the VM: myproject_default_1689947592479_50991
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 3389 (guest) => 53389 (host) (adapter 1)
    default: 5985 (guest) => 55985 (host) (adapter 1)
    default: 5986 (guest) => 55986 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: WinRM address: 127.0.0.1:55985
    default: WinRM username: vagrant
    default: WinRM execution_time_limit: PT2H
    default: WinRM transport: negotiate
An error occurred executing a remote WinRM command.

Shell: Cmd
Command: hostname
Message: Digest initialization failed: initialization error

The Vagrantfile I'm using is pretty vanilla:

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.box = "gusztavvargadr/windows-10"

  config.vm.synced_folder ".", "/kirby"

  config.vm.provider "virtualbox" do |vb|
    vb.gui = false
  end
  
  # wait longer for a slowly booting VM
  config.winrm.max_tries = 300 # default is 20
  config.winrm.retry_delay = 2 #seconds. This is the defaul value and just here for documentation.
  
  config.vm.provision "file", source: "requirements.txt", destination: "c:/Users/vagrant/requirements.txt"
  config.vm.provision :shell, upload_path: "c:/Users/vagrant/buildtools/", path: "buildtools/install_dependencies.ps1"
  config.vm.provision :shell, upload_path: "c:/Users/vagrant/buildtools/", path: "buildtools/install_requirements.ps1"
  config.vm.provision :shell, inline: "git config --global --add safe.directory '%(prefix)///vboxsvr/myproject/'"
end

I'm running macOS Ventura 13.4.1 (c) (22F770820d), Vagrant 2.3.7, VirtualBox 7.0.8.

The error message has changed a bit over the last version of the box file, but I'm really without an idea on how to fix or even debug this. The box seems to be running, but vagrant winrm fails, whereas vagrant ssh does work and lands me in cmd.exe.

@gusztavvargadr
Copy link
Owner

@markasbach thanks for reaching out.

This seems to be a regression in Vagrant itself, I've noticed it myself. I managed to make it work only by downgrading Vagrant itself, to me version 2.3.6 still works.

Please let me know if downgrading could solve your issue.

@markasbach
Copy link
Author

Indeed, downgrading to 2.3.6 helped. Thanks, I didn't find the issue in Vagrant (and had different issues with Ubuntu boxes hat 2.3.7 seems to solve ...).

@gusztavvargadr
Copy link
Owner

@markasbach thanks for confirming. Hope they release 2.3.8 soon with fixes for both these issues.

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

No branches or pull requests

2 participants