-
Notifications
You must be signed in to change notification settings - Fork 123
Not able to add paths to latest Docker Desktop File Sharing on MacOS Monterey #7519
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
Comments
Same for me |
It is likely that you are adding a path that is already shared at a parent level and Docker Desktop is silently discarding the new path. We will review and add a warning message to Desktop. Please let me know if that is not the case. |
This is not the case for me.. for example i have /opt/pp/logs that was added previously.. now im trying to add /opt/pp/data and it does not work.. i also tried to add my home directory using the file browser and it did not work either Docker Desktop 4.37.2 (179585) |
same issue |
same here |
bump: same issue, latest build. When adding directories not present, they are removed on 'apply and restart' And when launching a built image, it complains: WARN[0000] /users/name/Docker/coordemo/i14y-csv/docker-compose.yml: the attribute Version 4.38.0 (181591) Engine: 27.5.1 Compose: v2.32.4-desktop.1 Credential Helper: v0.8.2 Kubernetes: v1.31.4 |
Same issue! Docker Desktop 4.39.0 (184744) |
Requoting this reply because it was the fix. In my case, I was adding a subdirectory in my home tree, not noticing that the top two pre-configured lines were /Users and /Volumes (which is...basically everything on your Mac). Docker Desktop could certainly give an error message explaining why the line disappears to help explain why. This means you should configure your output as /Users/foo/bar/etc, it worked for me. |
Same issue here |
So I fixed my issue. I had to edit manually these files ~/Library/GroupContainersAlias/group.com.docker/settings.json and ~/Library/GroupContainersAlias/group.com.docker/settings-store.json to remove my old filesharess. I share on /opt/... After the edit I have /Users,/Volumes,/private and /tmp are there by default.. now my mounts work with this config |
I'm facing the same issue with the 4.35 and 4.39. Editing manually ~/Library/Group\ Containers/group.com.docker/settings.json doesn't help. As with everyone, docker desktop doesn't show the path in the GUI, and attempting to add it, result in the entry being removed when clicking the button Apply & Restart. Adding a path outside the home directory works fine. Note:
|
Same issue |
Same here with 4.40 |
Description
This bug may be similar to #7012
I can not add any new paths to latest docker Desktop on MacOS Monterey in Settings > Resources > Filesharing. After clicking the "Apply and restart"-Button the added paths in List disappear and docker does no save or restart at all. I tried to add the paths manually via the "settings.json" but with no luck.
Reproduce
1 Install Docker Desktop latest version for Mac (4.37.1)
2 Open Docker Desktop Settings and navigate to Resources > File Sharing
3 select the + and choose a folder
4 Hit apply and restart
Apply and restart just removes the added path and Docker Desktop Engine does no restart at all
Expected behavior
I would expect Docker Desktop to save my file path and allow me to mount volumes for a container
docker version
Version: 27.4.0 API version: 1.47 Go version: go1.22.10 Git commit: bde2b89 Built: Sat Dec 7 10:35:43 2024 OS/Arch: darwin/arm64 Context: desktop-linux Server: Docker Desktop 4.37.1 (178610) Engine: Version: 27.4.0 API version: 1.47 (minimum version 1.24) Go version: go1.22.10 Git commit: 92a8393 Built: Sat Dec 7 10:38:33 2024 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.7.21 GitCommit: 472731909fa34bd7bc9c087e4c27943f9835f111 runc: Version: 1.1.13 GitCommit: v1.1.13-0-g58aa920 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Diagnostics ID
43988214-2085-4E0D-8D38-FD559EB8D904/20250105123306
Additional Info
No response
The text was updated successfully, but these errors were encountered: