Source: blog.docksal.io
NFS access issues on macOS 10.15 (Catalina)Category: Docker
You’ve upgraded your Mac to macOS Catalina and your local dev environment based on Docker Desktop or VirtualBox/Vagrant stopped working and throws vague errors? Something like this: Or this for Docksal users (makes a bit more sense): You are not alone: Your project’s codebase likely resides under one of the standard user folders in macOS (e.g., Downloads, Documents, Desktop) or on an external drive.
Changes in the “Transparency, Consent, and Control” (TCC) framework in macOS 10.15 (Catalina) affected every local dev stack that utilized NFS for file sharing (whether using Vagrant/VirtualBox or Docker Desktop under the hood).
The NFS daemon does not have privileges to access user folders by default, meaning your dev stack cannot access them either in this chain: There are currently only two ways to solve this problem and neither can be automated behind the scenes.
If you are not feeling comfortable with your local development stack having access to your private user folders, then you will have to move your project’s codebase out of those folders.
Changes in the “Transparency, Consent, and Control” (TCC) framework in macOS 10.15 (Catalina) affected every local dev stack that utilized NFS for file sharing (whether using Vagrant/VirtualBox or Docker Desktop under the hood).
The NFS daemon does not have privileges to access user folders by default, meaning your dev stack cannot access them either in this chain: There are currently only two ways to solve this problem and neither can be automated behind the scenes.
If you are not feeling comfortable with your local development stack having access to your private user folders, then you will have to move your project’s codebase out of those folders.
Related Articles
Community Partners
DevOps Careers