for-mac icon indicating copy to clipboard operation
for-mac copied to clipboard

Changing of Settings -> Advanced -> Disk Image location fails

Open tengelmeier opened this issue 1 year ago • 17 comments

  • [x] I have tried with the latest version of Docker Desktop
  • [x] I have tried disabling enabled experimental features
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

After changing Settings -> Advanced -> Disk Image location to an external volume, either a.) docker restarts with no disk images or b.) docker moves existing images to the new location and restarts

Actual behavior

Beachball in settings forever, no data copied / moved to the new location (After some hours of beachballing I had a kernel panic / computer shut down, not sure if this is related)

After mac reboot I tried it again with the same result

Information

  • macOS Version: 13.3 (22E252)
  • Intel chip or Apple chip: Intel
  • Docker Desktop Version: v4.18.0

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

Looks like docker is not running while the settings are reapplied

/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
[2023-04-08T10:04:28.951323000Z][com.docker.diagnose][I] set path configuration to OnHost Starting diagnostics

[PASS] DD0027: is there available disk space on the host? [SKIP] 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? [FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": EOF [2023-04-08T10:04:28.984250000Z][com.docker.diagnose][I] ipc.NewClient: f1e501fd-diagnose -> diagnosticd.sock diagnosticsd [2023-04-08T10:04:28.984539000Z][com.docker.diagnose][I] (389bb27e) f1e501fd-diagnose C->S diagnosticsd GET /ping [2023-04-08T10:04:28.985536000Z][com.docker.diagnose][W] (389bb27e) f1e501fd-diagnose C<-S NoResponse GET /ping (975.999µs): Get "http://ipc/ping": EOF

[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": EOF [2023-04-08T10:04:28.986583000Z][com.docker.diagnose][I] ipc.NewClient: 05bd6aec-com.docker.diagnose -> lifecycle-server.sock VMDockerdAPI [2023-04-08T10:04:28.986984000Z][com.docker.diagnose][I] (e3fe61e0) 05bd6aec-com.docker.diagnose C->S VMDockerdAPI GET /docker [2023-04-08T10:04:28.988039000Z][com.docker.diagnose][W] (e3fe61e0) 05bd6aec-com.docker.diagnose C<-S NoResponse GET /docker (1.038599ms): Get "http://ipc/docker": EOF [...]

[PASS] DD0015: are the binary symlinks installed? [FAIL] DD0031: does the Docker API work? error during connect: Get "http://docker.raw.sock/v1.24/containers/json?limit=0": EOF [PASS] DD0013: is the $PATH ok? Error response from daemon: Bad response from Docker engine [FAIL] DD0003: is the Docker CLI working? exit status 1 [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? [PASS] 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? [WARN] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": EOF [WARN] DD0004: is the Docker engine running? Get "http://ipc/docker": EOF [PASS] DD0015: are the binary symlinks installed? [WARN] DD0031: does the Docker API work? error during connect: Get "http://docker.raw.sock/v1.24/containers/json?limit=0": EOF [WARN] DD0032: do Docker networks overlap with host IPs? error during connect: Get "http://docker.raw.sock/v1.24/networks": EOF

Steps to reproduce the behavior

df

tengelmeier avatar Apr 08 '23 10:04 tengelmeier