Navigation Menu

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

Use appropriate mount_option for 'parallels' provider (Apple Silicon Macs) #1481

Merged
merged 1 commit into from Mar 14, 2023

Conversation

code23-barna
Copy link
Contributor

For Apple Silicon Macs there is a section in the docs: https://roots.io/trellis/docs/vagrant/#parallels-apple-silicon-m1-macs but that page doesn't give much information about the configuration.

I suggest to mention there that after the duplication of the vagrant.default.yml, you have to change in the vagrant.local.yml file at least the vagrant_mount_type to:

vagrant_mount_type: 'parallels'

otherwise you will get the following error (hence the 'nfs' mount type):

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o vers=3 10.211.55.2:/path/to/site /vagrant-nfs-<SITENAME>

Stdout from the command:



Stderr from the command:

mount.nfs: access denied by server while mounting 10.211.55.2:/path/to/site

exit status 1

When you change the vagrant_mount_type to parallels the trellis up command will fails with:

Failed to mount folders in Linux guest. You've specified mount options
which are not supported by "prl_fs" file system.

Invalid mount options: ["dmode=755", "fmode=644"]
exit status 1

That's because dmode and fmode are VirtualBox specific options, we need to use a Parallels specific: share.

@swalkinshaw
Copy link
Member

Thanks for the details. Makes sense to me 🚀

@swalkinshaw swalkinshaw merged commit 68cbc41 into roots:master Mar 14, 2023
2 checks passed
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

Successfully merging this pull request may close these issues.

None yet

2 participants