docker/for-mac

gRPC FUSE unable to be disabled

daver12345 opened this issue · 13 comments

daver12345 commented
  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID: E7979FD6-5F14-487D-BABB-A3E6710EF646/20220901181021

Expected behavior

Able to disable gRPC FUSE, disable it then click the "Apply & Restart" button to save changes.

Actual behavior

Unable to disable gRPC FUSE, switch gets re-enabled after clicking the "Apply & Restart" button. Computer has been restarted and Docker has as well. On the latest version of Docker.

Information

  • macOS Version: 12.5.1
  • Intel chip or Apple chip: Apple M1, Macbook Air 2020
  • Docker Desktop Version: 4.12.0 (85629)

Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0001: is the application running?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0017: can a VM be started?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0012: is the VM networking working?
[PASS] DD0032: do Docker networks overlap with host IPs?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0019: is the com.docker.vmnetd process responding?
[PASS] DD0033: does the host have Internet access?
No fatal errors detected.

Steps to reproduce the behavior

  1. Click on Preferences
  2. Uncheck "Use gRPC Fuse for file sharing"
  3. Click "Apply & Restart"
  4. gRPC gets re-checked
nicks commented

Thanks for reporting! We have a fix in progress.

Right now, if you need to work around this, you should be able to open "~/Library/Group Containers/group.com.docker/settings.json" and add "useGrpcfuse": false to the file before starting docker desktop. (i agree this is not a great workaround)

  • 👍2
  • ❤️6
qFieldwire commented

@nicks

you should be able to open "~/Library/Group Containers/group.com.docker/settings.json" and add "useGrpcfuse": false to the file before starting docker desktop.

This does not work. For my system, there is not settings.json file in the folder. I created one and add the line but that doesn't do anything.

caricare2 commented

@nicks

you should be able to open "~/Library/Group Containers/group.com.docker/settings.json" and add "useGrpcfuse": false to the file before starting docker desktop.

This does not work.

It did work in my case. I'm assuming you did make sure Docker wasn't running when you made the change? It also seems to go away if Docker restarts. I created a function in my .bashrc to allow myself to fix it more easily:

# Fix docker gRPC
fixdocker() {
        sed -i .bak 's/"useGrpcfuse": true/"useGrpcfuse": false/' '/Users/yourusername/Library/Group Containers/group.com.docker/settings.json'
}
qFieldwire commented

@caricare2 Oh I see. I did not exit Docker. Yup! That works! Thanks!

dcraigmv commented

I've set useGrpcfuse to false and opened Docker Desktop but it seems to be unable to start, currently sifting through mac console logs. Nothing obvious yet.

  • 👍3
DianaAlcantara commented

I've set useGrpcfuse to false and opened Docker Desktop but it seems to be unable to start, currently sifting through mac console logs. Nothing obvious yet.

This is happening to me. I have the mount problem (operation not permitted) and when I set the flag to false in that json file, docker doesn't seem able to start

bneigher commented

Same.. when disabling gRPC Fuse on M1 Mac, Docker Desktop can no longer start making Docker unusable. On latest (4.13.1) and Mac OS X 12.6

  • 👍3
juanmolle commented

After 4.12 Docker is having problems in M1, I go back to that version

technotarek commented

Same problem here and the work around provided by @qFieldwire doesn't resolve the issue. Instead, after launching Docker Desktop, it gets stuck in the stopped state. If I change settings.json back to true for "useGrpcfuse", Docker Desktop loads up just fine. Is this still in the works? Perhaps the work around isn't sufficient on Ventura? Other ideas?

Docker Desktop 4.14.1; MacOs Ventura 13.0.1 on a MacBook Air with M2 chip

docker-robott commented

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

ccallebs commented

Still experiencing this with fresh Docker install on Ventura.

/remove-lifecycle stale

  • 👍1
dwelch2344 commented

Sadly this is burning me also

c0nscience commented

experiencing the same issue. I try to mount a folder from my host machine to a dev container:
OSX 13.5 (22G74)
Docker Desktop: 4.22.0 (117440)
Engine: 24.0.5