Skip to content
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

VMware issues (with workarounds) #5

Open
Kier opened this issue May 10, 2018 · 1 comment
Open

VMware issues (with workarounds) #5

Kier opened this issue May 10, 2018 · 1 comment

Comments

@Kier
Copy link

Kier commented May 10, 2018

The build scripts have a few issues when working with the vmware_desktop provider instead of the default virtualbox host - but thankfully they can be worked around as far as I can tell.

Vagrantfile

Obviously, the Vagrantfile needs some adjustment to work with VMware - and in some cases the edits are not obvious.

Firstly, the build scripts need to be told not to create a linked clone of the base box, otherwise packaging will fail later. The config additions look like this (as far as I can tell):

    config.vm.provider "vmware_desktop" do |vmware|
        vmware.linked_clone = false
    end

Secondly, the default scotchbox synced_folder config won't work with VMware, because the VMware version doesn't support dmode and fmode parameters, relying instead on umask config.

Therefore, we change the folder sync line as follows:

config.vm.synced_folder ".", "/var/www", :mount_options => ["umask=000"]

Apache installation

This has been a painful learning process, but it turns out that for some reason there is a permissions failure when attempting to install Apache due to it trying to create /var/www/html and failing, which results in Apache not being installed at all. This applies only to VMware, but the issue can be mitigated by creating a html folder in the folder along with the Vagrantfile and install.sh before attempting to run vagrant up.

Conclusion

I'll keep this updated with any further issues and workarounds I find, as I find them.

@Kier
Copy link
Author

Kier commented May 10, 2018

A few notes on the Apache issue:

geerlingguy/drupal-vm#247
resolved in
geerlingguy/drupal-vm@e4ee925

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant