Unable to run Docker with long username #6122
Description
- I have tried with the latest version of Docker Desktop
- I have tried disabling enabled experimental features
- I have uploaded Diagnostics
- Diagnostics ID: F2B99B1D-5D59-4612-814D-CEAABDAB7C70/20220103210640
Expected behavior
Install and run Docker Desktop.
Actual behavior
Unable to complete the Docker Desktop installation.
Information
- macOS Version: Monterey, version 12.1.
- Intel chip or Apple chip: Intel Core i9.
- Docker Desktop Version: 4.3.2 (72729)
Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
It doesn't look like this is valid. At this time docker is up and running and docker ps works fine and I can do a docker run just fine.
~ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
Starting diagnostics
[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?
[FAIL] DD0016: is the LinuxKit VM running? vm is not running: vm has not started
[PASS] DD0001: is the application running?
[PASS] DD0018: does the host support virtualization?
[FAIL] DD0017: can a VM be started? vm has not started: vm has not 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?
[FAIL] DD0012: is the VM networking working? network checks failed: failed to ping host: exit status 1
[003:22:29:50.493][I] ipc.NewClient: 8babb1ea-diagnose-network -> Library/Containers/com.docker.docker/Data/diagnosticd.sock diagnosticsd
[common/pkg/diagkit/gather/diagnose.runIsVMNetworkingOK()
[ common/pkg/diagkit/gather/diagnose/network.go:34 +0xc5
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x4e51960)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x4e51960)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2, 0x4e51960)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x4e51960, 0xc0006bd7d0)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x100000000000000, 0xc0006bd7d0)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0x4733cc0, 0xc00059f910)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x4e517e0, 0x0, {0xc00059fb18, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1ce
[main.checkCmd({0xc0001ae010, 0xc0001ae010, 0x4}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:130 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:96 +0x273
[003:22:29:50.493][I] (618c9a5c) 8babb1ea-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["192.168.178.19"]}
[003:22:29:50.998][E] (618c9a5c) 8babb1ea-diagnose-network C<-S 01262aaf-diagnosticsd POST /check-network-connectivity (505.81933ms): failed to ping host: exit status 1
[common/pkg/diagkit/gather/diagnose.runIsVMNetworkingOK()
[ common/pkg/diagkit/gather/diagnose/network.go:35 +0x13f
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x4e51960)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x4e51960)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2, 0x4e51960)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x4e51960, 0xc0006bd7d0)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x100000000000000, 0xc0006bd7d0)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0x4733cc0, 0xc00059f910)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x4e517e0, 0x0, {0xc00059fb18, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1ce
[main.checkCmd({0xc0001ae010, 0xc0001ae010, 0x4}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:130 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:96 +0x273
[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?
Please investigate the following 1 issue:
1 : The test: can a VM be started?
Failed with: vm has not started: vm has not started
The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.
Steps to reproduce the behavior
When using a long username and consequently a long home folder name (44 characters in my case), Docker is unable to start. It won't show any error on the screen, checking in the Activity Monitor the process is stuck in "Not responding" and just give up after some time. After renaming the home folder for something smaller, Docker started normally.
- Download and copy the Docker Desktop to the Applications folder.
- Try to run the Docker Desktop.
- The Docker Desktop won't open and in the Activity Monitor the process is "Not responding".
