search

docker / desktop-linux

Bug reports for Docker Desktop for Linux
https://docs.docker.com/desktop/linux/
77 stars 5 forks source link

Docker desktop writes "docker engine stopped" #139

Open VasKonstV opened 1 year ago

VasKonstV commented 1 year ago

Expected behavior

Normal running of Docker Desktop

Actual behavior

Docker Desktop gives a message that docker engine stopped But the Docker engine works normally: image

Information

Steps to reproduce the behavior

  1. Install docker engine
  2. Install and run docker desktop
VasKonstV commented 1 year ago

I tried to reinstall the docker desktop and i gor the following error: Download is performed unsandboxed as root as file '/home/vaskonst/docker-desktop-4.18.0-amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

VasKonstV commented 1 year ago

I made self diagnostics and the result is following: image

VasKonstV commented 1 year ago

I also uploaded diagnostics: Diagnostics ID: b6e8014b-6dfa-4582-84cd-a09db80f8c02/20230411082943 (uploaded) Here is the link: https://docker-pinata-support.s3.amazonaws.com/incoming/3/b6e8014b-6dfa-4582-84cd-a09db80f8c02/20230411082943.zip

VasKonstV commented 1 year ago

And finally I tried to do the following: modprobe kvm And I got an Error: modprobe: ERROR: could not insert 'kvm': Operation not permitted

VasKonstV commented 1 year ago

And finally my self-diagonstics: image image

VasKonstV commented 1 year ago

And and several warnings: 1 : The check: is the credentials store configured correctly? Produced the following warning: Error: password store is empty. Try "pass init".

The Credential Store is not set up correctly.

See https://docs.docker.com/desktop/get-started/#credentials-management-for-linux-users

2 : The check: are KVM user permissions configured? Produced the following warning: user must be added to the kvm group to access the kvm device, see https://docs.docker.com/desktop/install/linux-install/#kvm-virtualization-support

To start Docker Desktop, user must have access to the KVM device.

3 : The check: does the host support virtualization? Produced the following warning: stat /dev/kvm: no such file or directory

The Docker engine runs inside a Linux VM. Therefore the host must support virtualization.

Check that hardware-assisted virtualization (either Intel VMX or AMD SVM) and Data Execution Prevention (sometimes labeled XD or Execute Disable or NX) are enabled in your BIOS.

Check your bootloader is configured to launch Hyper-V.

See https://docs.docker.com/desktop/windows/troubleshoot/#virtualization

4 : The check: are KVM user permissions configured? Produced the following warning: user must be added to the kvm group to access the kvm device, see https://docs.docker.com/desktop/install/linux-install/#kvm-virtualization-support

To start Docker Desktop, user must have access to the KVM device.

5 : The check: does the host support virtualization? Produced the following warning: stat /dev/kvm: no such file or directory

The Docker engine runs inside a Linux VM. Therefore the host must support virtualization.

Check that hardware-assisted virtualization (either Intel VMX or AMD SVM) and Data Execution Prevention (sometimes labeled XD or Execute Disable or NX) are enabled in your BIOS.

Check your bootloader is configured to launch Hyper-V.

See https://docs.docker.com/desktop/windows/troubleshoot/#virtualization

6 : The check: can a VM be started? Produced the following warning: vm has not started: failed to open kmsg.log: open /home/vaskonst/.docker/desktop/log/vm/kmsg.log: no such file or directory

The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.

7 : The check: is the LinuxKit VM running? Produced the following warning: vm is not running: failed to open kmsg.log: open /home/vaskonst/.docker/desktop/log/vm/kmsg.log: no such file or directory

The Docker engine runs inside a Linux VM. Therefore the VM must be running.

8 : The check: are the LinuxKit services running? Produced the following warning: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory

The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.

9 : The check: is the Docker engine running? Produced the following warning: Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

10 : The check: does the Docker API work? Produced the following warning: Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?

If the Docker API is not available from the host then Docker Desktop will not work correctly.

11 : The check: do Docker networks overlap with host IPs? Produced the following warning: Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?

VasKonstV commented 1 year ago

And the result of diagnostics of KVM: INFO: Your CPU does not support KVM extensions KVM acceleration can NOT be used

bsousaa commented 1 year ago

it looks like your CPU does not support KVM which is required per the documentation at https://docs.docker.com/desktop/install/linux-install/#kvm-virtualization-support.

Mnish55 commented 1 year ago

issue

I have the same problem [ Docker engine stop ] also i face some additional issue who i uploaded above.

aiordache commented 1 year ago

@Mnish55 It looks like your credstore was corrupted. Can you try to delete ~/.password-store/docker-credential-helpers where desktop credentials are stored and then start Docker Desktop.