Setting Up Vagrant and VirtualBox Issues

fragicide

Bumping this. Anyone have any suggestions?

luceos

fragicide This is the first time I've used Vagrant, and I'm to the point where it's just easier doing my dev work through my VPS as usual. It's needlessly frustrating.

Exactly my thoughts after having played with homestead (vagrant for laravel) for a while. The hassle was too much and if you know how to maintain your development vm, there is nothing that can beat that..

As to your specific issue, it seems the commands you run are deprecated or unsupported, it feels like a version mismatch of vagrant versus that vagrantfile. Not sure whether this helps though 😉

fragicide

luceos Exactly my thoughts after having played with homestead (vagrant for laravel) for a while. The hassle was too much and if you know how to maintain your development vm, there is nothing that can beat that..

It's a damn shame. In theory, things like Vagrant could be so useful. Unfortunately, things like this happen that make it more frustrating, while making remote editing and development look easier.

luceos As to your specific issue, it seems the commands you run are deprecated or unsupported, it feels like a version mismatch of vagrant versus that vagrantfile. Not sure whether this helps though

Haha, not much help. I literally spent about 4 hours trying to figure this out to no avail.

luceos

fragicide You know in fact, I have developed with different set ups in the past. I came from kate (text editor with ssh functionality) and moved to phpstorm. In this last situation I worked with sshfs mounts, sftp and locally. And I must say that last situation is still the best, just install a webserver on my local machine and it's fast as hell 🙂

fragicide

luceos I come from the school of developing through FTP. It wasn't until around 2010 that I discovered XAMPP and started running a local server to develop stuff. I'm still oddly comfortable with SFTP development.

I wanted to try something new, and that something new decided to bite me in the ass. I guess old habits will have to stay 😛

Franz

fragicide Sorry for not getting back earlier...
This is probably because the shared folders are set up to use NFS. Windows usually does not support that. Do you have any (Vagrant) plugins installed?

(Also, even if it does, you will sooner or later hit problems with the allowed depth of nested directories being smaller in Windows than in Ubuntu - NPM generates a lot of nested node_modules folders...)

fragicide

So basically, it's better to just wait for my Macbook to use something like Vagrant.

Another reason to hate Windows haha.

Thanks @Franz

Franz

Yeah, I finally installed Ubuntu on my desktop computer to have a reasonable experience developing Flarum 😉

Kulga

Linux is always available 🙂

DSitC

Without an Unix-based OS, you're basically screwed. 😉

luceos

DSitC that's a bit drastic, there are plenty of people who get around using phpstorm (has integrated terminal and vcs functionality). But I agree, nothing beats a *nix based OS in development.

DSitC

luceos Nothing beats

ln -s ...

for me. 😉

SeeD

@fragicide After checking the Chinese support forums.

They adviced to do the following on line 100 onwards

  # A private dhcp network is required for NFS to work (on Windows hosts, at least)
  # Windows users should use the winnfsd plugin: https://github.com/GM-Alex/vagrant-winnfsd
  # config.vm.network :private_network, type: "dhcp"

  # Use NFS for the shared folder
  config.vm.synced_folder ".", "/vagrant",
            id: "core",
            :nfs => true,
            :mount_options => ['']

1. Comment config.vm.network
2. empy the array on mount options

Now it's working for me. Not sure for how long. LOL