kenjutsu
(Kenjutsu)
June 26, 2023, 10:22am
1
Hi,
I have installed Docker Desktop 4.20.1 (110738) on my MacBook Air M1, 2020 running macOS 13.4.
Under Settings → Resources → Advanced , I changed the Disk image location to my external SSD drive. After clicking on Apply & restart , all I get is the spinning blue “circle”. It has been doing this for more than 40 minutes now.
Any ideas?
Edit: Also, the selected folder on the SSD drive remains empty except for the created DockerDesktop folder that also remains empty
rimelek
(Ákos Takács)
June 26, 2023, 9:19pm
2
I don’t know the solution, but I tried to change the location now and I got the same result, although I didn’t wait for 40 minutes. My guess was Docker Desktop copied the data slowly so I copied the disk image manually in the automatically created “DockerDesktop” folder but that didn’t work, because the “DockerDesktop” folder was not empty. When I tried to set DockerDesktop as destination, it just created a new DockerDesktop folder inside it.
Fortunately when stopped Docker Desktop and started it again, it used the original folder so I didn’t break my environment.
My other guess was that macOS needs permission to write your SSD, but I used another folder my user’s home so it couldn’t be the problem for me and I couldn’t find any indication of copying in the logs.
tail -f "$HOME/Library/Containers/com.docker.docker/Data/log/host"/* | grep -i copy
The above command will give you warnings because there are directories there not just regular files, but I tried this to search for possible indications in all the log files. If you check the files sorted by time
cd "$HOME/Library/Containers/com.docker.docker/Data/log/host"
ls -latr
You will find log files changing because the host can’t reach the virtual machine which is not running, but I still couldn’t find out what was happening. Then I tried to search among the open issues and find it
opened 01:07PM - 13 Apr 23 UTC
version/4.18.0
- [x] I have tried with the latest version of Docker Desktop
- [x] I have tri… ed disabling enabled experimental features
- [x] I have uploaded Diagnostics
- Diagnostics ID: A86CC52E-36D4-4F96-B334-E7F775C2A92D/20230413123832
### Expected behavior
After changing Settings -> Resources -> Advanced -> Disk Image location to _external volume -> empty folder_, Docker should successfully change it to new location and restart.
### Actual behavior
After changing Settings -> Resources -> Advanced -> Disk Image location to an empty folder on external volume, Docker hangs forever on "Apply & restart", the circle of progress bar constantly spins. Docker service becomes inactive and hangs in restarting state.

If I try to do it for the same partition, where disk image originally was, it works as intended.
### Information
I did a clean install of Docker Desktop from the official site. Waited for it to finish changing directory for more than 30 mins. The directory to where I move is clean of any files. A disk space available is more than 100Gb on both drives, where Docker is installed and the directory, where I move. The disk is free of errors and the both volumes for Docker and where I move is internal disk of MacBook, which never failed and allows blazing fast disk access.
I also tried:
- Restart Docker or Quit and then start over with checking its not running in Activity Monitor
- Reboot and apply the setting again many times
- Checked the rights on the dir @ external drive, so I able to move files here, it's not write-protected
- No antivirus, at Little Snitch firewall Docker has full access to any outbound/inbound connection
- Fully reinstall with ```uninstaller /Applications/Docker.app/Contents/MacOS/uninstall``` and reboot for sure before installing again
- Stop Docker service and then change the dir to another
- Reduce disk limit and swap to the minimum values available, 8Gb for disk limit and 0Gb for swap respectively.
- macOS Version: Ventura 13.2.1
- Intel chip or Apple chip: Apple M1
- Docker Desktop Version: 4.18.0
### Output of `/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check`
```
[2023-04-13T12:40:46.973584000Z][com.docker.diagnose][I] set path configuration to OnHost
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?
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2023-04-13T12:40:46.983219000Z][com.docker.diagnose][I] ipc.NewClient: 69cbf4f4-diagnose -> diagnosticd.sock diagnosticsd
[2023-04-13T12:40:46.983437000Z][com.docker.diagnose][I] (f5619988) 69cbf4f4-diagnose C->S diagnosticsd GET /ping
[2023-04-13T12:40:46.983746000Z][com.docker.diagnose][W] (f5619988) 69cbf4f4-diagnose C<-S NoResponse GET /ping (303.834µs): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-04-13T12:40:46.984240000Z][com.docker.diagnose][I] ipc.NewClient: 3ad77a33-com.docker.diagnose -> lifecycle-server.sock VMDockerdAPI
[2023-04-13T12:40:46.984564000Z][com.docker.diagnose][I] (4db55475) 3ad77a33-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-04-13T12:40:46.984871000Z][com.docker.diagnose][W] (4db55475) 3ad77a33-com.docker.diagnose C<-S NoResponse GET /docker (304.875µs): Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-04-13T12:40:46.985083000Z][com.docker.diagnose][I] (4db55475-1) 3ad77a33-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-13T12:40:46.985309000Z][com.docker.diagnose][W] (4db55475-1) 3ad77a33-com.docker.diagnose C<-S NoResponse GET /ping (224.709µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-04-13T12:40:47.985670000Z][com.docker.diagnose][I] (4db55475-2) 3ad77a33-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-13T12:40:47.988156000Z][com.docker.diagnose][W] (4db55475-2) 3ad77a33-com.docker.diagnose C<-S NoResponse GET /ping (2.485708ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-04-13T12:40:48.989218000Z][com.docker.diagnose][I] (4db55475-3) 3ad77a33-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-13T12:40:48.991239000Z][com.docker.diagnose][W] (4db55475-3) 3ad77a33-com.docker.diagnose C<-S NoResponse GET /ping (2.127042ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-04-13T12:40:49.992449000Z][com.docker.diagnose][I] (4db55475-4) 3ad77a33-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-13T12:40:49.994634000Z][com.docker.diagnose][W] (4db55475-4) 3ad77a33-com.docker.diagnose C<-S NoResponse GET /ping (2.176041ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-04-13T12:40:50.995807000Z][com.docker.diagnose][I] (4db55475-5) 3ad77a33-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-13T12:40:50.998085000Z][com.docker.diagnose][W] (4db55475-5) 3ad77a33-com.docker.diagnose C<-S NoResponse GET /ping (2.26975ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-04-13T12:40:51.999422000Z][com.docker.diagnose][I] (4db55475-6) 3ad77a33-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-13T12:40:52.001589000Z][com.docker.diagnose][W] (4db55475-6) 3ad77a33-com.docker.diagnose C<-S NoResponse GET /ping (2.164125ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-04-13T12:40:53.002692000Z][com.docker.diagnose][I] (4db55475-7) 3ad77a33-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-13T12:40:53.004767000Z][com.docker.diagnose][W] (4db55475-7) 3ad77a33-com.docker.diagnose C<-S NoResponse GET /ping (2.068667ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-04-13T12:40:54.006103000Z][com.docker.diagnose][I] (4db55475-8) 3ad77a33-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-13T12:40:54.008382000Z][com.docker.diagnose][W] (4db55475-8) 3ad77a33-com.docker.diagnose C<-S NoResponse GET /ping (2.2805ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[FAIL] DD0015: are the binary symlinks installed? 2 errors occurred:
* checking binaries in /usr/local/bin: looking for /usr/local/bin/docker: lstat /usr/local/bin/docker: permission denied
* checking binaries in $HOME/.docker/bin: unable to find /Users/Rage/.docker/bin: stat /Users/Rage/.docker/bin: no such file or directory
[FAIL] DD0031: does the Docker API work? Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?
[FAIL] DD0013: is the $PATH ok? unable to find docker executable on PATH
[FAIL] DD0003: is the Docker CLI working? exec: "docker": executable file not found in $PATH
[PASS] DD0038: is the connection to Docker working?
[FAIL] DD0014: are the backend processes running? 3 errors occurred:
* com.docker.vpnkit is not running
* com.docker.driver.amd64-linux is not running
* com.docker.virtualization is not running
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[FAIL] DD0010: is the Docker API proxy responding? failed to ping Docker proxy API with error: Get "http://ipc/desktop-diagnostics/ping": read unix ->/Users/Rage/.docker/run/docker.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2023-04-13T12:40:55.747620000Z][com.docker.diagnose][I] ipc.NewClient: be681834-diagnose -> <HOME>/.docker/run/docker.sock Proxy
[2023-04-13T12:40:55.747962000Z][com.docker.diagnose][I] (2962e667) be681834-diagnose C->S Proxy GET /desktop-diagnostics/ping
[2023-04-13T12:40:56.749688000Z][com.docker.diagnose][W] (2962e667) be681834-diagnose C<-S NoResponse GET /desktop-diagnostics/ping (1.001707834s): Get "http://ipc/desktop-diagnostics/ping": read unix -><HOME>/.docker/run/docker.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2023-04-13T12:40:56.751581000Z][com.docker.diagnose][I] (2962e667-1) be681834-diagnose C->S Proxy GET /ping
[2023-04-13T12:40:57.754142000Z][com.docker.diagnose][W] (2962e667-1) be681834-diagnose C<-S NoResponse GET /ping (1.002534333s): Get "http://ipc/ping": read unix -><HOME>/.docker/run/docker.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2023-04-13T12:40:58.756890000Z][com.docker.diagnose][I] (2962e667-2) be681834-diagnose C->S Proxy GET /ping
[2023-04-13T12:40:59.759177000Z][com.docker.diagnose][W] (2962e667-2) be681834-diagnose C<-S NoResponse GET /ping (1.002291042s): Get "http://ipc/ping": read unix -><HOME>/.docker/run/docker.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2023-04-13T12:41:00.761361000Z][com.docker.diagnose][I] (2962e667-3) be681834-diagnose C->S Proxy GET /ping
[2023-04-13T12:41:01.763714000Z][com.docker.diagnose][W] (2962e667-3) be681834-diagnose C<-S NoResponse GET /ping (1.002354334s): Get "http://ipc/ping": read unix -><HOME>/.docker/run/docker.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2023-04-13T12:41:02.766400000Z][com.docker.diagnose][I] (2962e667-4) be681834-diagnose C->S Proxy GET /ping
[2023-04-13T12:41:03.769550000Z][com.docker.diagnose][W] (2962e667-4) be681834-diagnose C<-S NoResponse GET /ping (1.003080042s): Get "http://ipc/ping": read unix -><HOME>/.docker/run/docker.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[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": dial unix diagnosticd.sock: connect: no such file or directory
[WARN] DD0004: is the Docker engine running? Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[WARN] DD0015: are the binary symlinks installed? 2 errors occurred:
* checking binaries in /usr/local/bin: looking for /usr/local/bin/docker: lstat /usr/local/bin/docker: permission denied
* checking binaries in $HOME/.docker/bin: unable to find /Users/Rage/.docker/bin: stat /Users/Rage/.docker/bin: no such file or directory
[WARN] DD0031: does the Docker API work? Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?
[WARN] DD0032: do Docker networks overlap with host IPs? Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?
```
### Steps to reproduce the behavior
1. Start Docker
2. Go to 'Settings -> Resources -> Advanced -> Disk Image location'
3. Change location to empty folder of external drive, which is not protected from the read/write
4. See the app hangs as on the screen I provided above
You can read the suggestions there and comment to share your experience.
Update:
I found this topic which is very similar to this issue except that is related to Windows:
This issue got fixed with Docker Desktop 4.20.0: