-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to boot VM after following instructions in CONTRIBUTING.md for local BLT development setup #2890
Comments
Well, I've got a work around at least. I had to add the blt directory in two separate places in the VM. Adding the below to the vagrant_synced_folders array in box/config.yml did the job.
|
The work around I described above is encoded in PR #2900. I don't love it, but don't have a better solution at the moment. |
At least one other user has told me they do not have the same issue, even after confirming we're using the same versions of BLT, vagrant, and virtualbox. Can anyone replicate the problems I'm seeing? |
Yes, I get the same error when following the same steps. For what it's worth, I don't see where CONTRIBUTING.md* implies that this should work, although it obviously would be nice if it did. It looks like BLT is fairly clever and tries to mount itself in Vagrant in a way that you can traverse the symlink both on the host and in the VM. But for the purposes of the post-provision script, the mount doesn't work, because the post-provision scripts execute from the Note that It seems like the solution is force DrupalVM to run the scripts from *For anyone else following along at home, the new location for CONTRIBUTING.md is https://github.com/acquia/blt/blob/9.x/docs/CONTRIBUTING.md |
If you are using BLT Version 12.x or Higher the path of the directory got changed to
So you need to chnage the PATH of file inside
|
Correction, third line is also to a
At least that was my case with BLT 12.8.2. |
My system information:
When I follow the directions in CONTRIBUTING.md to set up an environment for developing BLT locally, when running
vagrant up
in the resulting environment, booting the VM fails with the following errors:It appears there are two factors causing this:
The text was updated successfully, but these errors were encountered: