This repository has been archived by the owner on May 10, 2023. It is now read-only.
Migrate from VirtualBox to Parallels #23
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch drops VirtualBox in favour of Parallels as the virtualisation backend since Parallels runs on both Intel and Apple silicon Macs.
We also switch to using SSHFS to implement fielsystem sharing between the host and VM instead of Parallels built in folder sharing. I'm not sure why but Parallels built in folder sharing causes loads of permission issues. For whatever reason SSHFS works well, at the cost of increased CPU usage and worse fs performance.
chowncurrently fails inside the guest on the SSHFS mount, which means containers that usechownwill also fail. This might be resolvable by passing some options to SSHFS to give the guest complete control over the host fs.