Docker Desktop keeps spinning when restarted after setting file sharing implementation to osxfs (Legacy)

[ShanikaEdiriweera]

Description

Hi
I have added a file sharing directory /maven due to the error -

docker: Error response from daemon: Mounts denied: 
The path /maven/.m2 is not shared from the host and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> Resources -> File Sharing.

Then I have selected the file sharing implementation to osxfs (Legacy) following this discussion #5390, and
due to the following error I got

docker: Error response from daemon: error while creating mount source path '/host_mnt/maven/settings.xml': mkdir /host_mnt/maven: input/output error.

When I restart after setting osxfs, docker desktop keeps spinning and restarting. Tried resetting to factory settings several times. But no luck!

Reproduce

1. add a file sharing directory /maven
2. selected the file sharing implementation to osxfs (Legacy)
3. apply & restart docker desktop

Expected behavior

Docker desktop should restart

docker version

Client:
 Cloud integration: v1.0.33
 Version:           24.0.2
 API version:       1.43
 Go version:        go1.20.4
 Git commit:        cb74dfc
 Built:             Thu May 25 21:51:16 2023
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

docker info

Client:
 Version:    24.0.2
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.10.5
    Path:     /Users/sed/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.18.1
    Path:     /Users/sed/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/sed/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.19
    Path:     /Users/sed/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.4
    Path:     /Users/sed/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/sed/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/sed/.docker/cli-plugins/docker-scan
  scout: Command line tool for Docker Scout (Docker Inc.)
    Version:  v0.12.0
    Path:     /Users/sed/.docker/cli-plugins/docker-scout

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 24.0.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 3dce8eb055cbb6872793272b4f20ed16117344f8
 runc version: v1.1.7-0-g860f061
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.15.49-linuxkit-pr
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 6
 Total Memory: 7.667GiB
 Name: docker-desktop
 ID: db4b2051-abb3-49af-8050-f3d8968d7099
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

Diagnostics ID

0D6F343D-FDEF-4188-BCB8-F459DB59B272/20230602022541

Additional Info

Self diagnostics output:

Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[FAIL] DD0004: is the Docker engine running? docker engine is still starting, initializing dockerd for 1m47.854081792s
[2023-06-02T02:24:19.473607000Z][com.docker.diagnose][I] ipc.NewClient: d6c29311-com.docker.diagnose -> lifecycle-server.sock VMDockerdAPI
[2023-06-02T02:24:19.473631000Z][com.docker.diagnose][I] (d2e3b35c) d6c29311-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-06-02T02:24:19.475686000Z][com.docker.diagnose][I] (d2e3b35c) d6c29311-com.docker.diagnose C<-S 0aa639cd-VMDockerdAPI GET /docker (2.03425ms): {"current_action":"initializing dockerd","current_action_start":"2023-06-02T02:22:31.621652208Z","engine":"starting","error":""}

[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? Get "http://docker.raw.sock/v1.24/containers/json": context deadline exceeded
[PASS] DD0013: is the $PATH ok?
[FAIL] DD0003: is the Docker CLI working? signal: killed
[PASS] DD0038: is the connection to Docker working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[SKIP] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[WARN] DD0004: is the Docker engine running? docker engine is still starting, initializing dockerd for 1m47.854081792s
[PASS] DD0015: are the binary symlinks installed?
[WARN] DD0031: does the Docker API work? Get "http://docker.raw.sock/v1.24/containers/json": context deadline exceeded
[WARN] DD0032: do Docker networks overlap with host IPs? Get "http://docker.raw.sock/v1.24/networks": context deadline exceeded

Please note the following 3 warnings:

1 : The check: is the Docker engine running?
    Produced the following warning: docker engine is still starting, initializing dockerd for 1m47.854081792s

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

2 : The check: does the Docker API work?
    Produced the following warning: Get "http://docker.raw.sock/v1.24/containers/json": context deadline exceeded

If the Docker API is not available from the host then Docker Desktop will not work correctly.

3 : The check: do Docker networks overlap with host IPs?
    Produced the following warning: Get "http://docker.raw.sock/v1.24/networks": context deadline exceeded

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address


Please investigate the following 1 issue:

1 : The test: is the Docker engine running?
    Failed with: docker engine is still starting, initializing dockerd for 1m47.854081792s

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

[TonyWu1995]

i have same problem

[aamargant]

I have the same issue

[fredericdalleau]

Is it mandatory to share /maven? On my Mac, writing on / is prevented by Mac OS. I'd suggest to test with ~/maven.

[ShanikaEdiriweera]

In my case it was a misunderstanding from my end!
Trying to share /maven is trying to share a directory called /maven in the root, which I didn't have.
The maven directory I had was deep within /Users directory in my repo, which was already shared!

Why I initially got The path /maven/.m2 is not shared from the host and is not known to Docker. error was because of an incorrect environment variable pointing to /maven in the root.

Hope this helps!