Docker Desktop Version 4.11.1 stuck in status "Docker Desktop starting..."

Abdullah-Albinali commented 2 years ago

[ x] I have tried with the latest version of Docker Desktop
[ ] I have tried disabling enabled experimental features
[x ] I have uploaded Diagnostics
Diagnostics ID: e364f375-2257-4f98-8a82-9c220ba4d07c/20220808040140

Expected behavior

Docker Desktop to run

Actual behavior

Docker Desktop is stuck at "Docker Desktop starting..." as well as when i click on settings the application is stuck loading

Information

i am unable to disable/enable experimental features as the settings page is stuck loading

its my first time trying to install Docker Desktop, and i ran into this problem, when trying to even run docker ps i was getting an error "Error response from daemon: dial unix docker.raw.sock: connect: no such file or directory"

when i changed the docker context from "desktop-linux" to "default" the docker ps command now works and i can rundocker run hello-world and get a proper result, but the Docker Desktop is still stuck at "Docker Desktop starting..."

Linux distro: Ubuntu (this is a vm running on a windows host (virtual box) i have verified that kvm is working on it.)
Distro version: 22.04.1 LTS
Docker Desktop Version: 4.11.1

Steps to reproduce the behavior

run the Docker Desktop either from the "application" or from command line via systemctl --user start docker-desktop

onattech commented 2 years ago

Same thing happened to me when I had virtualbox running. Closed virtualbox and Docker Desktop started.

p1-0tr commented 2 years ago

hi @Abdullah-Albinali, the first thing I'd do is make sure your windows host has sufficient space to let your VM's drive expand (if it can't, DD's VM drive won't be able to expand, and will prevent it from working). The next thing would be to make sure DD's VM drive is not corrupted for some reason, to do that just remove ~/.docker/desktop/vms/0/data/Docker.raw (it will get re-created when DD starts, but you'll loose container and images created in DD, but since this is a fresh install, I presume this will not be an issue). Finally you can manually adjust resources allocated to the DD VM by editing ~/.docker/desktop/settings.json, specifically memoryMiB (it controls VM RAM allocation, I wouldn't go below 1024) and diskSizeMiB. Let me know if any of this helps.

Abdullah-Albinali commented 2 years ago

@p1-0tr , thanks for the update, i checked the free disk space for my VM using dfcommand and it shows it still has around 80GB of free disk space available, i also checked the memory usage and 5GB memory is available to be used.

i then went and deleted the VM drive as suggesetd in ~/.docker/desktop/vms/0/data/Docker.raw and then rebooted the VM, but till its stuck at "Docker Desktop starting..."

after some time GNOME reported the app crashed with the below trace.

Stacktace
#0 0x0000559553e1cd63 in ?? ()
No symbol table info available.
Backtace stopped: Cannot access memory at address 0x7ffed0e58200

i also checked the ~/.docker/desktop/settings.json and noticed it was assigned 2539.

still not sure what is going wrong with docker desktop, i tried to uninstall and reinstall it again but the same issue persists

to uninstall i did the following:

sudo apt remove docker-desktop
sudo apt remove docker-ce docker-ce-cli docker-ce-rootless-extras docker-compose-plugin docker-scan-plugin
sudo apt autoremove
rm -r $HOME/.docker/desktop
sudo rm /usr/local/bin/com.docker.cli
sudo apt purge docker-desktop
cd ~/.config/systemd/user/
rm docker.service
rm -rf ~/.local/share/docker/

and then reinstalled, but same issue , stuck at "Docker Desktop starting..."

p1-0tr commented 2 years ago

@Abdullah-Albinali - just to be sure, did you check if the windows host isn't running low on disk space? df in the VM will report what's allocated, rather than actually available. So if you are using an image format that adjusts dynamically (e.g. qcow2 will usually not preallocate), you can over provision its size, e.g. you could create a 100GB image on a partition with only 20GB available, and run into issues only when the disk image needs to expand beyond the available space.

Abdullah-Albinali commented 2 years ago

@p1-0tr , yes the host windows machine has around 500 GB of free space

mefron commented 2 years ago

I'm seeing the same thing. I'm running Fedora on a Window's machine running a VM using VirtualBox. I've upgraded to 4.12.0 but saw the same behavior on 4.11. Both the host OS and the VM has plenty of disk space and memory. I'm not seeing any error messages.

docker-robott commented 1 year ago

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

docker-robot[bot] commented 1 year ago

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

docker / desktop-linux