Error launching Mutable Instruments Vagrant Environment

#1

I’m new here, so sorry if this is a stupid question. I’m struggling to launch the Mutable Instruments virtual environment, I have followed the steps at https://github.com/pichenettes/mutable-dev-environment, but when I run “vagrant up” I get the following message;

default: Cloning into ‘eurorack-modules’…
default: fatal: unable to access ‘https://github.com/pichenettes/eurorack.git/’: gnutls_handshake() failed: Close notify
default: /tmp/vagrant-shell: line 31: cd: /vagrant/eurorack-modules: No such file or directory
default: fatal: Not a git repository (or any parent up to mount point /vagrant)
default: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
default: fatal: Not a git repository (or any parent up to mount point /vagrant)
default: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

Can anyone help?

1 Like
#2

Probably too late to help the OP, but for anyone else having this problem…

I’ve spent hours trying to get this set up in Windows 7 SP1. As far as I can tell, it’s down to which versions of the various things needed that you install.

I seem to have finally got past the stage of seeing different error messages, and this is what I have so far:

VirtualBox-5.1.26-117224-Win.exe

then

Oracle_VM_VirtualBox_Extension_Pack-5.1.26-117224.vbox-extpack

from :
https://www.virtualbox.org/wiki/Download_Old_Builds_5_1

then

vagrant_2.2.4_i686.msi

from:

To get vagrant to work, I had to update PowerShell. Win 7 comes with v2, and we need v3 or later. Allegedly, an older version of Vagrant could also work - but it didn’t for me.

To get PowerShell updated, I installed Windows Management Framework 4.0. That relies on .NET 4.5 or later - and apparently, you need the whole thing, not just the usual client part installed.

This article was useful, for that part, though the .NET version check part of it didn’t work, for me:

https://mikefrobbins.com/2015/01/08/how-to-check-the-powershell-version-and-install-a-new-version/

If, like me, you’re not familiar with using PowerShell, you’ll want to read the first part of this article, first - commands he gives in the main article are for PowerShell, not the Windows command line, and this tells you how to use it:

https://mikefrobbins.com/2015/01/01/where-to-find-and-how-to-launch-powershell/

As I said, I’ve only got to the part where “vagrant up” seems to have worked, so far, so this may be premature. I thought I’d better write it down while I remember some of it.