desktop-linux icon indicating copy to clipboard operation
desktop-linux copied to clipboard

Docker Desktop not starting on Ubuntu 22.04 LTS When Login to the system as root user

Open geilige opened this issue 3 years ago • 34 comments

I have tried with the latest version of Docker Desktop I have tried disabling enabled experimental features I have uploaded Diagnostics INFO[0044] Uploaded diagnostics to: https://docker-pinata-support.s3.amazonaws.com/incoming/3/65d5994c-7ed7-4406-9851-23d54839b6bd/20220609081335.zip Diagnostics ID: 65d5994c-7ed7-4406-9851-23d54839b6bd/20220609081335 (uploaded)

Expected behavior Docker desktop starts up

Actual behavior Message: Docker Desktop stopped

Information Linux distro: 22.04 LTS Distro version: Ubuntu Docker Desktop Version: docker-desktop-4.9.0-amd64 Steps to reproduce the behavior Install docker desktop Docker desktop won't startup

Keep up the good work!

geilige avatar Jun 09 '22 08:06 geilige

I can confirm this also happens on PopOS (based off Ubuntu) following an upgrade from 21.04 to 22.04.

Logs show the following:

Jun 9 10:38:38 pop-os [email protected][2203]: unable to update icon for Docker Desktop1 Jun 9 10:38:43 pop-os [email protected][2203]: Docker Desktop1, Impossible to lookup icon for 'Docker Desktop1_2344-panel' in path /tmp/.org.chromium.Chromium.6jjrUn Jun 9 10:38:43 pop-os [email protected][2203]: unable to update icon for Docker Desktop1 Jun 9 10:38:47 pop-os com.docker.backend[9891]: [2022-06-09T09:38:47.793412895Z][com.docker.backend][W] still waiting to update HTTP proxy on http-proxy-control.sock after 4m0.612149585s. Last error was Post "http://localhost/vm/httpproxy": dial unix <HOME>/.docker/desktop/http-proxy-control.sock: connect: no such file or directory Jun 9 10:38:47 pop-os com.docker.backend[9891]: [2022-06-09T09:38:47.793253845Z][com.docker.backend][W] e07af7f9-PauseHDL /pause/events server not replying: Get "http://ipc/pause/events": dial unix <HOME>/.docker/desktop/procd.sock: connect: no such file or directory

R70YNS avatar Jun 09 '22 09:06 R70YNS

Same problem here using Ubuntu 22.04. No way to make it start, Always same message saying it's stopped, and " unix /.docker/desktop/procd.sock: connect: no such file or directory" in logs

Conkernel avatar Jun 11 '22 21:06 Conkernel

I uninstalled docker-desktop 4.9.0, and install 4.8.2. Then it works. https://docs.docker.com/desktop/release-notes/#docker-desktop-482

hangingman avatar Jun 12 '22 13:06 hangingman

Fixed this problem by enabling virtualisation from the BIOS settings.

gurpreet-fe avatar Jun 13 '22 13:06 gurpreet-fe

I have this exact same issue, and I have tried about everything...

I see a couple people recommended fixes, and those do not work in my situation. 4.8.2, same issue, same error as OP reports.

Virtualization is already enabled in the BIOS, KVM et al work without fail on this same system. Docker worked just fine on this system prior to the upgrade / reinstall to 22.04. Will not work whatsoever on 22.04.

DBACHRY13 avatar Jun 14 '22 22:06 DBACHRY13

the same issue... Created plain user, logged in, stared Docker Desktop and it works like a charm. But on administrative right user it won't run.

Please assist. And recommendations for virtualization in bios looks dummy...

Just to be clear docker is running as a daemon perfectly well but UI is not running...

vabarmovych-corcentric avatar Jun 17 '22 15:06 vabarmovych-corcentric

Fixed this problem by enabling virtualization from the BIOS settings.

I tried this after having this issue and now is working

LucasHartridge avatar Jun 27 '22 10:06 LucasHartridge

i was having the same issue and now its resolved, i did two things that has not been previously mentioned.

  1. Because my home folder is encrypted using ecryptfs, i moved the $HOME/.docker folder to outside the home folder, and created a symlink so $HOME/.docker folder is still valid for docker-desktop to write to.

  2. Ran this, as this folder was not accessable by the current user - not sure if this did anything though: sudo chmod a+rw /var/lib/docker

runawaycoin avatar Jul 05 '22 09:07 runawaycoin

I am having the same issue on Arch with 4.9 and 4.10. Downgrading to 4.8.2 works.

alexanderczigler avatar Jul 06 '22 08:07 alexanderczigler

I just installed docker desktop 4.10.1 in ubuntu 22.04 LTS and it is working fine

Taz03 avatar Jul 16 '22 09:07 Taz03

I assumed my hypervisor(proxmox) had "nested virtualization" already enabled for the VM's to use. This is incorrect, see YouTube. I recommend the environment work direction migrate to the beginning of the docker install work direction and how to research and verify virtualization for bare metal and hypervisor/VM setups. Currently this work direction is at the end (almost a footnote). If not properly setup will yield the "stopped" in docker desktop. OS: Ubuntu 22.04 dektop-amd64.iso, docker: 5:20.10.17~3-0~ubuntu-jammy/docker-desktop-4.10.1-amd64.deb, 2022-07-16. Anyway, this was my experience and hope it helps others. I do not know yet, but likely this has contributed to rancher not running correctly either.

gene1234 avatar Jul 16 '22 15:07 gene1234

I've recently installed docker 20.10.10 and docker-desktop-4.11.0-amd64.deb on Ubuntu 22.04.1 LTS and docker desktop Docker Desktop stopped... but I expect starting

IgorZaporozhtsev avatar Sep 19 '22 08:09 IgorZaporozhtsev

FYI I had a similar issue with versions above 4.8.2, this is what worked for me: https://github.com/docker/desktop-linux/issues/32#issuecomment-1161436024

jcreixell avatar Sep 30 '22 12:09 jcreixell

Ran this sudo chmod a+rw /var/lib/docker as pointed by @runawaycoin and that worked for me

kbajpai avatar Nov 20 '22 19:11 kbajpai

Please install gnome-terminal it works for me sudo apt install gnome-terminal i found it from here https://computingforgeeks.com/install-docker-desktop-on-ubuntu/

imharisaa avatar Jan 12 '23 08:01 imharisaa

Same problem.

Settings > General > "Start Docker Desktop when you log in" is checked, but it never starts on its own - I always have to do it manually.

Docker Desktop 4.14.1 on Ubuntu 20.04.5

odigity avatar Jan 19 '23 00:01 odigity

After reading from syslog, I've noticed that the HOME/.docker permissions are not set for my user. creating <HOME>/.docker/desktop: mkdir <HOME>/.docker/desktop: permission denied After setting the permissions the problem was solved.

sudo chown $USER:$USER -R ~/.docker

shuvalp avatar Jan 25 '23 00:01 shuvalp

For anyone using Docker via VM Ware Ubuntu image, remember to turn on the "Virtualize Intel VT..." settings in the: Virtual Machine Settings / Processors

Sylanvys avatar Jan 26 '23 06:01 Sylanvys

Running latest version (4.16.2) on Ubuntu 22.04. Checked the box and doesn't start. Nothing for Docker in the syslog. I have no folder called /var/lib/docker. Home folder is set to my user and group. Virtualization is enabled in BIOS.

Edit: I was able to get it to start on login by running this command:

systemctl --user enable docker-desktop

Bovive avatar Jan 28 '23 21:01 Bovive

In my case, I installed ubuntu on VMWare workstation pro 15, I installed the docker desktop and faced the same issue "docker desktop stopped..". I then checked VM settings and fund I forgot to enable virtualization. After checking two checkbox namely

  • Virtualize Intel VT-x/EPT or AMD-V/RVI
  • Virtualize IOMMU (10 memory management unit) and restarting my VM my docker desktop started working

image

hguptauk avatar Feb 19 '23 23:02 hguptauk

Running latest version (4.16.2) on Ubuntu 22.04. Checked the box and doesn't start. Nothing for Docker in the syslog. I have no folder called /var/lib/docker. Home folder is set to my user and group. Virtualization is enabled in BIOS.

Edit: I was able to get it to start on login by running this command:

systemctl --user enable docker-desktop

This command works for me!

tungdt-90 avatar May 10 '23 16:05 tungdt-90

After trying so many solutions it didn't worked!!! I came up with solution, follow these steps:

  1. Try to run Docker Desktop using command line. systemctl --user start docker-desktop
  2. If not started, then use this command instead. systemctl --user force-reload docker-desktop

Hope it works for you guys as well!

TahirIqbalGit avatar Jul 17 '23 08:07 TahirIqbalGit

FYI - The "Start Docker Desktop when you log in" setting has never worked for me once in the last two years since I started using Docker Desktop - not on Ubuntu, Linux Mint, or macOS. I've been manually starting it every time I boot my computer.

Running systemctl --user enable docker-desktop as myself seems to have worked. Thanks!

odigity avatar Aug 08 '23 15:08 odigity

This works for me here

muneebable avatar Aug 28 '23 13:08 muneebable

I installed the latest version recently 4.25.0 and still had the same issue. Ensured virtualization is enabled, enabled service, added permissions etc. still nothing.

Reverting back to 4.8.2 and it worked fine.

R70YNS avatar Nov 02 '23 10:11 R70YNS

Tried installing the latest version of Docker (4.25.0 at the time of writing this) on an Asus Rog Strix G15 with an AMD processor and nothing worked. Had to install Docker 4.8.2 as well.

JuanDiegoAW avatar Nov 06 '23 14:11 JuanDiegoAW

i've forgot to check this page's instructions. It worked for me.

SoltanReza avatar Nov 09 '23 22:11 SoltanReza

From: https://stackoverflow.com/questions/75907472/docker-desktop-does-not-launch-on-ubuntu-failed-to-start-docker-desktop-service

Update March 2024:

The previously opened issue has been closed. This is because the workaround (from the original answer) has been accepted as the solution

Original answer:

It turns out this is an open issue on the docker desktop-linux (Docker Desktop for Linux) repository on GitHub.

The solution is to unmask the service and enable it.

Solution:

$ file /etc/xdg/systemd/user/docker-desktop.service

Running the command above, you should notice that the file is a symlink to /dev/null

Delete the file: $ sudo rm /etc/xdg/systemd/user/docker-desktop.service

And then enable the service for the user: $ systemctl --user enable docker-desktop

sb5m avatar Apr 13 '24 22:04 sb5m

У меня ubuntu 24.04 и мне помогло здесь

AndreyXoma avatar May 09 '24 03:05 AndreyXoma

use sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 making it work on Ubuntu, the LTS version, worked for me

agrpranjal07 avatar May 11 '24 13:05 agrpranjal07