VirtualBox not correctly detected

[rmccue]

No description provided.

[jazzsequence]

+1 this problem.
have added existing Chassis projects to Desktop and they are not showing up in the app.

[rmccue]

@jazzsequence That looks more likely to be #3 I think.

[ptasker]

This seems to be a thing. Just tried out the beta and I'm getting a notice that both Vagrant and Virtual Box aren't installed.

Vagrant is installed in /usr/local/bin/vagrant

[ptasker]

Interestingly, if I clone the repo and run npm start the deps are picked up correctly. Build might just be out of date?

[rmccue]

The build should be fresh (the About screen should say 0.2.0). I wonder if there's weird permissions happening with the built version though.

[rmccue]

For those experiencing this problem: what does which VirtualBox output for you on the command line?

[ptasker]

/usr/local/bin/VirtualBox for me.

[zu]

same for me
/usr/local/bin/VirtualBox

[aheckler]

same: /usr/local/bin/VirtualBox

[ericnicolaas]

Similar (possibly the same) issue for me. In my case, the projects are all shown as running even though they are not up. Running "Launch" for any of them results in this:

which VBoxManage returns /usr/local/bin/VBoxManage

which VirtualBox returns /usr/local/bin/VirtualBox

[rmccue]

Interesting, I'll have to investigate further! Thanks for the feedback folks.

My suspicion on why this is occurring is that we pass through the environment variables to the shell we're running. For production builds, these are launched independently of an existing shell, so my guess is that the PATH variable isn't set correctly for this scenario.

I'll work on debugging and replicating this.

[danielck]

I can confirm this is happening on a fresh install of Chassis Desktop with no previous Chassis installation. I have previous installations of both Virtualbox and Vagrant for other reasons.

Virtualbox location: /usr/local/bin/Virtualbox
Vagrant location: /usr/local/bin/vagrant

[pjv]

Same. Fresh 0.2 install of Chassis Desktop.

[BronsonQuick]

I can also replicate VirtualBox not being detected correctly.

[rmccue]

Manged to replicate this locally properly. 👍

[rmccue]

Caught the bug, as I mentioned, it's to do with the environment variables being passed through. For me, the PATH used inside the app is /usr/bin:/bin:/usr/sbin:/sbin, whereas it's fine when running via the shell (which is how I did all the development). Apologies for this!

Investigation revealed the fix-path package, which fixes the issue pretty easily, but had to do some extra work to avoid (dumb) webpack warnings.

[tomjn]

As a sidenote, you can use an absolute path instead for a super quickfix with /usr/local/bin/vagrant, as well as vbox-img

[BronsonQuick]

Hey folks, I've just published a new release that should hopefully solve this issue: https://github.com/Chassis/Desktop/releases/tag/0.2.1

[ericnicolaas]

Unfortunately I'm still hitting issues with this after updating to 0.2.1:

Running VBoxManage from the command line works as expected.

[orionrush]

I think this issue is still in play as I'm running OSX 10.11.6 and Chassis Desktop 0.2.1, and it does not recognise that I have both Vagrant 2.0.4 and VB 5.2.10 installed.