CLOUD-3175: Fix Docker Volume Issues on M2/M3 Macs by Enabling VZ Emulation and virtiofs #90
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 PR addresses the Docker volume issues encountered by users on M2 and M3 Macs, as reported in this thread: rancher-sandbox/rancher-desktop#1209
@cobbr2 just had a rough time with this one on his m2 mac. He was seeing similar permission errors when trying to mount host volumes, preventing services like PostgreSQL from starting correctly.
We were able to resolve the underlying issue by switching from the default QEMU emulation to VZ (Virtualization.framework) and enabling virtiofs for file sharing between the host and the guest VM.
The PR reintroduces the necessary configuration changes that were previously removed, as these are still required for M2 and M3 Macs running Rancher Desktop. This also adds the fix to prevent needing to manually select virtiofs to get it working too.