I’m getting the following error when attempting to update my dev install on Windows. I first did a git pull, then vagrant up, vagrant ssh, and finally bundle install. The error occurs when trying to run bundle exec rake db:migrate vagrant@discourse:/vagrant$ bundle exec rake db:migrate rake aborted! ln: failed to create symbolic link '/vagrant/public/plugins/discourse-narrative-bot': Protocol error /vagrant/lib/discourse.rb:26:in `execute_command' /vagrant/lib/plugin/instance.rb:368:in `activate!' /vagrant/lib/discourse.rb:126:in `block in activate_plugins!' /vagrant/lib/discourse.rb:123:in `each' /vagrant/lib/discourse.rb:123:in `activate_plugins!' /vagrant/config/application.rb:179:in ` ' /vagrant/config/application.rb:27:in ` ' /vagrant/config/application.rb:26:in ` ' /vagrant/rakefile:5:in `require' /vagrant/rakefile:5:in ` ' /home/vagrant/.rvm/gems/ruby-2.3.1/gems/rake-12.0.0/exe/rake:27:in ` ' /home/vagrant/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `eval' /home/vagrant/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in ` ' (See full trace by running task with --trace)

Looks like its related to this line: [image] jomaxro: ln: failed to create symbolic link ‘/vagrant/public/plugins/discourse-narrative-bot’: Protocol error Did you already install the discobot plugin before this? Do we normally create symlinks or is that a vagrant thing?

[image] blake: Did you already install the discobot plugin before this? Nope, haven’t updated in quite some time. Also never installed plugins in Vagrant. [image] blake: Do we normally create symlinks or is that a vagrant thing? I have no idea…

It does not appear to be working: vagrant@discourse:/vagrant$ touch temp vagrant@discourse:/vagrant$ ln -s temp temp-link ln: failed to create symbolic link 'temp-link': Protocol error vagrant@discourse:/vagrant$

check this out https://github.com/mitchellh/vagrant/issues/6024 I didn’t read the whole thing, but you might need to downgrade to a different version of vagrant if they haven’t fixed it yet.

I would recommend avoiding vagrant, if you need a “quick” setup just start an ubuntu VM and and use our docker dev env.

Sounds good Sam - will test that out later today.

you need special rights to create symbolic links with windows (inside virtual machines), the right goes by “SeCreateSymbolicLink”. Administrator have this right by default. When you run vagrant up/ssh, you need to run it with a user that has this right. I avoided this error by starting a powershell as administrator (since I didn’t want to bother with granting rights to my user) and discourse is up and running

Unable to update vagrant dev install on Windows

Development

blake (Blake Erickson) June 12, 2017, 9:31pm 4

Can you just try creating a test symlink yourself and see if it works?

Topic		Replies	Views
Rake aborted message is showing when installing vagrant development Development	12	3053	January 2, 2018
Hgfs shared filesystem in VMWare does not support symlinks Development	6	6259	December 27, 2017
Installing locally through vagrant Self-hosting	17	4240	October 10, 2016
Error installing with vagrant for developent Development	0	670	April 2, 2017
»vagrant up« hangs Development	5	1978	April 5, 2018

Unable to update vagrant dev install on Windows

Related topics