Open renatopanda opened 5 years ago
Thanks for reporting this. Unfortunately, I don't have a Windows machine that I can test on. I know why this happens, but the fix may not be obvious. In the meantime, can you use the box at all? The part that's failing shouldn't affect the majority of the box's functionality. The change was to make it easier to push gems and work with git from inside the box, but the fix appears only to work for Linux and perhaps MacOS hosts.
I can't because it fails on vagrant up saying that I need to fix the errors and then try again. If you have any suggestion let me now and I will happily try it. Cheers.
I don't have access to a Windows machine. I would appreciate it if someone can try one of the V6.1.1 boxes from https://app.vagrantup.com/jadesystems, and let me know if it works, or at least doesn't cause a blocking failure.
Using the same image jadesystems/rails-jade-18-04-pg (virtualbox, 6.1.1)
, now I get the following (2x the first error):
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:
File provisioner:
* File source must be specified.
* File source must be specified.
I'm having the same issue on macOS catalina 10.15.1 VirtualBox 6.0.14 and Vagrant 2.2.6.
I've tried the jadesystems/rails-jade-16-04-pg (v6.1.1)
, jadesystems/rails-jade-18-04-pg (v6.1.1)
and jadesystems/rails-jade-18-04-mssql (v6.1.1)
boxes and they all return the same error
File provisioner:
* File source must be specified.
* File source must be specified.
Thanks for the updates, and sorry for the slow response. I'll have to back out those changes (as nice as they are for those of us on Linux), and re-think how to do this.
In case this helps others, starting from the previous box (5-2) you can use rails 6 by running:
// update rails to latest (6.x), for some reason had to use sudo
sudo gem install rails
//update node since a newer version is needed
sudo apt-get update nodejs -y
Trying rails new .
will fail on windows hosts because webpack (included with rails 6) creates symlinks on the shared folder but windows/vagrant will not allow that by default.
In those cases, the solution is enabling symlinks in vagrant by adding to the Vagrantfile:
config.vm.provider "virtualbox" do |v|
v.customize ["setextradata", :id, "VBoxInternal2/SharedFoldersEnableSymlinksCreate/v-root", "1"]
end
For this to work vagrant up
needs to run with administrator privileges so open a terminal (e.g., git bash) with admin privileges (right click, "run as admin").
Thanks for the updates. The next release will include a newer Node version (#41). I've noted your question about needing sudo
for updating Rails (#42). I may a get a chance to work on (#37) soon. We'll try your suggestions for running Vagrant as admin.
I'm currently testing boxes that shouldn't error when provisioning a new box, to fix the current issue (#38).
I uploaded to https://app.vagrantup.com/jadesystems version 6.2.0 of all four boxes. I hope it soles the error in file provisioner problem. Let me know if it works.
still get this on macOS catalina
Hi, The host is win7 with the latest virtualbox and vagrant (also tested on win10). Simply running the commands:
results in:
Can't figure out why but the older box works as expected (rails-5-2).
Thanks!