Open bro-aero opened 2 years ago
Hi @bro-aero. The logs in the diagnostics bundle you uploaded point to a kvm setup issue:
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: failed to initialize KVM: No such file or directory
Docker Desktop is running a VM and for that it needs kvm virtualization support. Please follow the instructions in the install docs to enable the module and set up device access.
Right, yes makes sense, thanks for pointing that out.
I thought I had followed that step during installation, but looking at it now it appears my CPU does not support KVM.
Any chance I can use qemu somehow rather than kvm?
@bro-aero - sorry, we don't have an option to run without kvm. And adding it would have a massive performance penalty. Did you make sure you have enabled virtualisation in the BIOS (https://bce.berkeley.edu/enabling-virtualization-in-your-pc-bios.html)?
Hi, @bro-aero
How are you doing? I got the same issue, and I didn't fix it yet.
According to @aiordache's advice, I checked the kvm setup, and I found a problem.
I logged out, and then logged in, and I saw my user didn't have permssion.
Not any solution? I still have same problem,please help me guys :(
Hi, @bro-aero How are you doing? I got the same issue, and I didn't fix it yet. According to @aiordache's advice, I checked the kvm setup, and I found a problem.
![]()
I logged out, and then logged in, and I saw my user didn't have permssion.
This is to add you to the kvm group, just use groups
to check
I checked kvm and everything is fine, but I still can't start docker desktop.
And I was able to start it normally at first, the problem appeared after a reboot of the computer, when it was solved after restarting the application, but now I can't fix it no matter how much I restart
Bro I checked my pc because of this and working on laptop now ,it is working now ..maybe ı didnt do correct setup on first pc thats why...here installed it with steps that docker shows on documents for ubuntu
Hi, I already fixed my issue on my vm ubuntu through this post. I'd appreciate if it's a bit of help for you to start docker. https://stackoverflow.com/questions/72281976/docker-is-running-docker-desktop-says-docker-desktop-stopped
This command works for me and also chek for vm enabled in you bios
systemctl --user start docker-desktop
I had the same problem. Here is the solution, which worked for me:
For Other Laptops, please check the Bios settings and set Hyper-V or Virtualization to Enabled while starting your OS and save and exit.
I had the same problem. Here is the solution, which worked for me:
1. Enabled Intel VMX in BIOS (AMD virtualization if you have AMD CPU) 2. Followed https://docs.docker.com/desktop/install/linux-install/#kvm-virtualization-support
Thank you very much. Problem solved!!
I got a Docker Desktop stopped...
message just after editing "Shared path" in its settings and clicking "Save and restart". Very annoying that a simple settings editing may break Docker Desktop. Still don't know how to fix it.
UPD:
To break Docker Desktop follow these steps:
"Settings" --> "Resources" --> "File sharing" --> add /opt/pysetup
directory --> click "Save and restart"
after set kvm group, i logout and login to take effect , and systemctl --user start docker-desktop.
@AIGeneratedUsername
I got a
Docker Desktop stopped...
message just after editing "Shared path" in its settings and clicking "Save and restart". Very annoying that a simple settings editing may break Docker Desktop. Still don't know how to fix it.
I encountered the exact same problem, manually editing the config /home/$USER/.docker/desktop/settings.json
helped.
"filesharingDirectories": [
" /snap/phpstorm/", <------ that was a problem. Removing the leading space helped.
"/home"
],
it's definitely a bug, сreated the issue - https://github.com/docker/desktop-linux/issues/122
@AIGeneratedUsername
I got a
Docker Desktop stopped...
message just after editing "Shared path" in its settings and clicking "Save and restart". Very annoying that a simple settings editing may break Docker Desktop. Still don't know how to fix it.I encountered the exact same problem, manually editing the config
/home/$USER/.docker/desktop/settings.json
helped."filesharingDirectories": [ " /snap/phpstorm/", <------ that was a problem. Removing the leading space helped. "/home" ],
it's definitely a bug, сreated the issue - #122
Thanks for this ... I had a path to a drive that was no longer mounted (automatically added by a rust MongoDB package) -- removing it from settings.json
allowed Docker Desktop to start
@m1k439 Yeah, same for me, added another issue - https://github.com/docker/desktop-linux/issues/132
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
Issue solved on unbuntu 23.04 on running on intel, had to enable virtualization in BIOS as said above, thanks
Expected behavior
To be honest, as I'm new to docker desktop I don't know what to expect specifically, but I'm assuming I should have options to start new containers etc.
Actual behavior
docker-desktop displays the message "Docker Desktop stopped" and it seems like most options/actions are unusable.![image](https://user-images.githubusercontent.com/109927345/180670592-6b74af74-dc9b-43ba-a039-f070da7ec460.png)
Information
This machine is running Ubuntu 20.04.4 LTS and it's not a VM Note: I am willing to try any suggestions that may help, however I have already tried:
Also note: when installing docker-desktop I have been downloading docker-desktop-4.10.1-amd64.deb and installing using the ubuntu software manager.
I'm able to reproduce this by opening docker-desktop, however I'm assuming this could be caused by some conflict with something that is specific to my machine, so as for re-creating an environment, I'm not sure.
Thanks in advance to anybody that has suggestions or can help.
Let me know if I have missed any details or info, happy to add more.