Docker desktop stopped working after upgrading Ubuntu from 23.10 to 24.04 #209

md-owes · 2024-04-27T09:24:43Z

Description

I upgraded my Ubuntu OS from 23.10 to 24.04 via sudo do-release-upgrade -d command and the upgrade was successful without any issue. However, after the upgrade and system restart, when i start docker desktop, it did not respond to clicking the docker desktop icon via app launcher. Thinking it might be due to system upgrade i decided to uninstall docker desktop 4.29 and reinstalled the same version but still docker desktop was unable to start. I verified the logs located at ~/.docker/desktop/log/host and there were no entries with keyword 'error' or 'fail'. I verified the service docker-desktop was enabled and running via command systemctl --user status docker-desktop but the command systemctl --user status docker gave error "Unit docker.service could not be found".

Reproduce

upgrade Ubuntu from any version (i upgraded from 23.10 but i believe it could be any version) to 24.04 via "sudo do-release-upgrade -d"
restart system
Start docker desktop

Expected behavior

Docker desktop should run with all my images and containers intact

docker version

terminal gets stuck while running this command but docker --version prints the below output 

Docker version 26.1.0, build 9714adc

docker info

terminal gets stuck while running this command

Diagnostics ID

7D75123F-C60D-4C2F-A751-FAC458B49182/20240427092253

Additional Info

No response

The text was updated successfully, but these errors were encountered:

andinianst93 · 2024-04-27T21:14:11Z

I have the same problem too. The Docker engine works fine though. It just I can not open the UI.

wgrs · 2024-04-27T21:26:35Z

Docker Desktop not working for me on Ubuntu 24.04 fresh install

luiz-fernandoalves · 2024-04-28T00:30:59Z

I freshly installed Ubuntu 24.04, and now Docker Desktop is not launching. I followed the official installation instructions (which worked for me on version 22.04), but it's still not successful.

raza2022 · 2024-04-28T07:43:23Z

Same so I can confirm the official installation was completed successfully, but Docker Desktop is not launching in Ubuntu 24.04

Steps

install fresh Ubuntu version 24.04
follow the Docker official instructions
Launch Docker Desktop

serious-angel · 2024-04-28T10:40:37Z

terminal gets stuck while running this command

Have you tried stracing the "stuck" command in order to find out what or when the exact sys-call or loop hangs?

Not to mention Linux and not Windows cases, have you tried not using Docker Desktop at all but marvelous and fairly sufficient CLI or... TUI at least?

beelzick · 2024-04-28T15:23:38Z

Same error here

md-owes · 2024-04-29T00:01:58Z

Apologies for tagging but looking for some eyes here asap as my work is completely dependent on it. @christophermclellan, @aiordache, @bsousaa

ptdatta · 2024-04-29T02:48:09Z

Same issue for me too. If I ran it from /opt/docker-desktop/bin/docker-desktop it say docker desktop starting but it never starts.

vic-reis · 2024-04-29T06:54:21Z

Seguimos triste, irei tentar instalar a versão 22 do ubunto para ver se é questão de compatibilidade do sistema, pois, a extensão do VSCODE segue com o mesmo erro.

Arnispl · 2024-04-29T11:03:59Z

I did these steps and now it works fine.

Remove the System-Level Mask
You need to remove the symbolic link that's masking the service at /etc/systemd/user/. Because this involves system-level changes, you'll need to use sudo:

sudo rm /etc/systemd/user/docker-desktop.service

Reload Systemd
2. After removing the symlink, reload the systemd daemon to apply the changes:

systemctl --user daemon-reload

3.Unmask at the User Level (if still needed)
If the service is still showing as masked at your user level, unmask it:

systemctl --user unmask docker-desktop

Start Docker Desktop
Try starting the Docker Desktop service again:

systemctl --user start docker-desktop

Check the Service Status
Confirm that the service is active and no longer masked:

systemctl --user status docker-desktop

Lapakin · 2024-04-29T12:32:00Z

I did these steps and now it works fine.
1. Remove the System-Level Mask
   You need to remove the symbolic link that's masking the service at /etc/systemd/user/. Because this involves system-level changes, you'll need to use sudo:
sudo rm /etc/systemd/user/docker-desktop.service

Reload Systemd 2. After removing the symlink, reload the systemd daemon to apply the changes:

systemctl --user daemon-reload

3.Unmask at the User Level (if still needed) If the service is still showing as masked at your user level, unmask it:

systemctl --user unmask docker-desktop
4. Start Docker Desktop
   Try starting the Docker Desktop service again:
systemctl --user start docker-desktop
5. Check the Service Status
   Confirm that the service is active and no longer masked:
systemctl --user status docker-desktop

Unfortunately, this didn't help me, as the file was not in the folder.

mayurDayal2000 · 2024-04-29T14:20:18Z

Hello, I encountered the same issue with the Docker Desktop GUI not loading. I managed to resolve it by navigating to /opt/docker-desktop/bin in the file system, right-clicking on com.docker.backend, and choosing 'Run'. This got Docker up and running for me. However, it seems to be stuck at the 'starting the Docker engine' loading screen now. Hope this helps anyone else facing the same problem!

serious-angel · 2024-04-29T14:43:33Z

Apologies for tagging but looking for some eyes here asap as my work is completely dependent on it. @christophermclellan, @aiordache, @bsousaa

As mentioned above, have you tried stracing to define and locate the issue causer? I don't have such issues, so I - cannot.

ptdatta · 2024-04-29T14:51:50Z

systemctl --user status docker-desktop

Hey @Arnispl I tried your solution but in my case, it just stuck at the starting stage.
I can see the service is running but every docker command is stuck. I tried with docker ps -a

simon-curtis · 2024-04-29T19:07:15Z

Hello, I encountered the same issue with the Docker Desktop GUI not loading. I managed to resolve it by navigating to /opt/docker-desktop/bin in the file system, right-clicking on com.docker.backend, and choosing 'Run'. This got Docker up and running for me. However, it seems to be stuck at the 'starting the Docker engine' loading screen now. Hope this helps anyone else facing the same problem!

Can confirm this worked for me too. And I am getting the same result, loading screen with no interactivity. Tools like docker compose just hang with no output

$ sudo systemctl is-active docker
active

$ docker info
Client: Docker Engine - Community
 Version:    26.1.0
 Context:    desktop-linux
 Debug Mode: false
//... truncated
Server:
ERROR: Cannot connect to the Docker daemon at unix:///home/simon/.docker/desktop/docker.sock. Is the docker daemon running?

Same output after running sudo systemctl start docker

Tried using sudo dockerd and go this:

$ sudo dockerd
INFO[2024-04-29T20:14:51.791691352+01:00] Starting up
failed to start daemon, ensure docker is not running or delete /var/run/docker.pid: process with PID 2292 is still running

So tried again

$ sudo rm /var/run/docker.pid
$ sudo dockerd
INFO[2024-04-29T20:18:59.472233212+01:00] Starting up
INFO[2024-04-29T20:18:59.472991190+01:00] detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf
failed to start daemon: error while opening volume store metadata database (/var/lib/docker/volumes/metadata.db): timeout

**** Restarted PC

$ sudo systemctl status docker
● docker.service - Docker Application Container Engine
     Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: enabled)
     Active: active (running) since Mon 2024-04-29 20:28:07 BST; 1min 49s ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 2299 (dockerd)
      Tasks: 18
     Memory: 107.1M (peak: 108.2M)
        CPU: 785ms
     CGroup: /system.slice/docker.service
             └─2299 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

Apr 29 20:28:06 simon-P330-server dockerd[2299]: time="2024-04-29T20:28:06.661678638+01:00" level=info msg="Starting up"
Apr 29 20:28:06 simon-P330-server dockerd[2299]: time="2024-04-29T20:28:06.665620700+01:00" level=info msg="detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf"
Apr 29 20:28:06 simon-P330-server dockerd[2299]: time="2024-04-29T20:28:06.744609074+01:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
Apr 29 20:28:06 simon-P330-server dockerd[2299]: time="2024-04-29T20:28:06.748766463+01:00" level=info msg="Loading containers: start."
Apr 29 20:28:07 simon-P330-server dockerd[2299]: time="2024-04-29T20:28:07.234483033+01:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
Apr 29 20:28:07 simon-P330-server dockerd[2299]: time="2024-04-29T20:28:07.382076738+01:00" level=info msg="Loading containers: done."
Apr 29 20:28:07 simon-P330-server dockerd[2299]: time="2024-04-29T20:28:07.414289859+01:00" level=info msg="Docker daemon" commit=c8af8eb containerd-snapshotter=false storage-driver=overlay2 version=26.1.0
Apr 29 20:28:07 simon-P330-server dockerd[2299]: time="2024-04-29T20:28:07.414658784+01:00" level=info msg="Daemon has completed initialization"
Apr 29 20:28:07 simon-P330-server dockerd[2299]: time="2024-04-29T20:28:07.505601417+01:00" level=info msg="API listen on /run/docker.sock"
Apr 29 20:28:07 simon-P330-server systemd[1]: Started docker.service - Docker Application Container Engine.

Spikhalskiy · 2024-04-29T19:44:43Z

Attaching a full journalctl --user -u docker-desktop.service -f log of systemctl --user start docker-desktop on Ubuntu 24.04.

Pieces that look relevant:


Apr 29 15:35:16 workstation com.docker.backend[45615]: [2024-04-29T19:35:16.040465382Z][com.docker.backend.tasks][E] supervisor detected that task has died with an error: shutdown with exit code 1: docker
Apr 29 15:35:16 workstation com.docker.backend[45615]: [common/cmd/com.docker.backend/supervisor/tasks.monitor({0x31a35a8, 0xc00034c000}, {0xc0004bafb0?, 0x2?}, 0xc000c31e10)
Apr 29 15:35:16 workstation com.docker.backend[45615]: [        common/cmd/com.docker.backend/supervisor/tasks/supervisor.go:73 +0xf3
Apr 29 15:35:16 workstation com.docker.backend[45615]: [common/cmd/com.docker.backend/supervisor/tasks.Supervise.func2()
Apr 29 15:35:16 workstation com.docker.backend[45615]: [        common/cmd/com.docker.backend/supervisor/tasks/supervisor.go:47 +0xce
Apr 29 15:35:16 workstation com.docker.backend[45615]: [common/cmd/com.docker.backend/supervisor/tasks.Supervise in goroutine 139
Apr 29 15:35:16 workstation com.docker.backend[45615]: [        common/cmd/com.docker.backend/supervisor/tasks/supervisor.go:46 +0x1f3
Apr 29 15:35:16 workstation com.docker.backend[45615]: [2024-04-29T19:35:16.040572545Z][com.docker.backend.tasks][I] shutting down 1 tasks
Apr 29 15:35:16 workstation com.docker.backend[45615]: [2024-04-29T19:35:16.040586300Z][com.docker.backend.tasks][I] shutdown group 0/0: [docker]
Apr 29 15:35:16 workstation com.docker.backend[45615]: [2024-04-29T19:35:16.040598472Z][com.docker.backend.tasks][I] all 1 tasks shutdown
Apr 29 15:35:16 workstation com.docker.backend[45615]: 145265-Services.startCLIMetrics: supervising tasks: task failed: shutdown with exit code<INT>: docker
Apr 29 15:35:16 workstation com.docker.backend[45615]: [2024-04-29T19:35:16.040674649Z][com.docker.backend.services][I] CLI metrics failed: supervising tasks: task failed: shutdown with exit code 1: docker

Apr 29 15:35:16 workstation com.docker.backend[45615]: [2024-04-29T19:35:16.112511919Z][com.docker.backend.electron][E] electron shutdown by signal: trace/breakpoint trap
Apr 29 15:35:16 workstation com.docker.backend[45615]: [common/cmd/com.docker.backend/internal/electron.open.func1()
Apr 29 15:35:16 workstation com.docker.backend[45615]: [        common/cmd/com.docker.backend/internal/electron/electron.go:215 +0x2e7
Apr 29 15:35:16 workstation com.docker.backend[45615]: [common/cmd/com.docker.backend/internal/electron.open in goroutine 31
Apr 29 15:35:16 workstation com.docker.backend[45615]: [        common/cmd/com.docker.backend/internal/electron/electron.go:190 +0x34c
Apr 29 15:35:16 workstation com.docker.backend[45615]: [2024-04-29T19:35:16.122171962Z][com.docker.backend.features][I] unleash client successfully synced with server
Apr 29 15:35:16 workstation com.docker.backend[45615]: [2024-04-29T19:35:16.122776101Z][com.docker.backend.features][E] unleash:  segment does not exist
Apr 29 15:35:16 workstation com.docker.backend[45615]: [common/cmd/com.docker.backend/internal/features.(*debugListener).OnError(0xc0002fa1b0, {0x316eae0, 0xc000526290})
Apr 29 15:35:16 workstation com.docker.backend[45615]: [        common/cmd/com.docker.backend/internal/features/unleashremote.go:107 +0x11e
Apr 29 15:35:16 workstation com.docker.backend[45615]: [github.com/Unleash/unleash-client-go/v3.(*Client).sync(0xc000dea000)
Apr 29 15:35:16 workstation com.docker.backend[45615]: [        github.com/Unleash/unleash-client-go/v3@v3.9.2/client.go:210 +0x388
Apr 29 15:35:16 workstation com.docker.backend[45615]: [created by github.com/Unleash/unleash-client-go/v3.NewClient.func1 in goroutine 581
Apr 29 15:35:16 workstation com.docker.backend[45615]: [        github.com/Unleash/unleash-client-go/v3@v3.9.2/client.go:129 +0x56

docker-dektop-service.log

Spikhalskiy · 2024-04-29T19:51:10Z

✅ I was able to solve this issue with

sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

It looks like an Electron and Chromium issue electron/electron#41066
and the above workaround was originally suggested in electron/electron#41066 (comment)

UPD:
You can create a file /etc/sysctl.d/20-apparmor.conf or /etc/sysctl.d/60-apparmor-namespace.conf containing

kernel.apparmor_restrict_unprivileged_userns = 0

and it will make this setting permanent. It's a good idea to remove it when the fix to electron and Docker Desktop is released.

simon-curtis · 2024-04-29T19:53:11Z

Worked for me, just running systemctl --user restart docker-desktop after:

$ sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
$ systemctl --user restart docker-desktop

and docker deskop UI pops up immediately. Thank you!

serious-angel · 2024-04-29T20:06:32Z

I was able to solve this issue by running
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
It looks like it's an Electron issue electron/electron#41066 and this workaround suggested in electron/electron#41066 (comment)

Related: moby/moby#47480 (rootless (non-dpkg): update docs and dockerd-rootless-setuptool.sh check for Ubuntu 24.04 (kernel.apparmor_restrict_unprivileged_userns)...)

sebasalas · 2024-04-29T20:32:29Z

I was able to solve this issue by running
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
It looks like it's an Electron and Chromium issue electron/electron#41066 and this workaround was suggested in electron/electron#41066 (comment)

It worked for me, thanks!!!

ptdatta · 2024-04-30T01:15:57Z

Worked for me too thanks.

luiz-fernandoalves · 2024-04-30T01:49:09Z

Worked for me, just running systemctl --user restart docker-desktop after:
$ sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
$ systemctl --user restart docker-desktop
and docker deskop UI pops up immediately. Thank you!

This operation works for me. Thanx !!!

tuberquia2115 · 2024-04-30T02:21:39Z

Worked for me, just running systemctl --user restart docker-desktop after:
$ sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
$ systemctl --user restart docker-desktop
and docker deskop UI pops up immediately. Thank you!

Thank you so much !! It's been hours and nothing has solved it and your answer saved me from staying up late

luiz-fernandoalves · 2024-04-30T04:44:41Z

I followed the instructions and now I can start Docker Desktop without running the commands. However, there is a security issue.

file: /usr/lib/sysctl.d/10-apparmor.conf 


 If it is desired to disable this restriction, it is preferable to create an
 additional file named **/etc/sysctl.d/20-apparmor.conf** which will override this
 current file and sets this value to 0 rather than editing this current file

kernel.apparmor_restrict_unprivileged_userns = 0

kartikeya-lyzr · 2024-04-30T12:28:16Z

Worked for me, just running systemctl --user restart docker-desktop after:
$ sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
$ systemctl --user restart docker-desktop
and docker deskop UI pops up immediately. Thank you!

This resolved my issue as well. Thank you
I just hope disabling apparmor_restrict_unprivileged_userns is not a security risk on desktop linux. I was facing the same issue. docker version was getting stuck and opening Docker Desktop did nothing.

serious-angel · 2024-04-30T12:37:48Z

$ sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
$ systemctl --user restart docker-desktop
This resolved my issue as well. Thank you I just hope disabling apparmor_restrict_unprivileged_userns is not a security risk on desktop linux. I was facing the same issue. docker version was getting stuck and opening Docker Desktop did nothing.

Have you checked out references mentioned above?

In a report from Google, 44% of the exploits they saw required unprivileged user namespaces as part of their exploit chain...
Therefore, for Ubuntu, we are introducing restricted unprivileged user namespaces, where AppArmor can be used to selectively allow and disallow unprivileged user namespaces. An AppArmor policy is used to selectively control access to unprivileged user namespaces on a per applications basis.
As such, unprivileged processes will only be able to create user namespaces if they are confined and have the "userns," rule in their AppArmor profile (or if they have CAP_SYS_ADMIN). Since it is not feasible to create a complete AppArmor profile for most affected applications, we introduced a new default_allow profile mode. While this effectively allows the application to remain unconfined, it also adds a new “userns,” rule to allow it to use unprivileged user namespaces.
Source

When specified in this manner, an application that is confined by such an AppArmor profile will be allowed to create new unprivileged user namespaces...
...the new kernel sysctl does place a restriction on unconfined applications, by denying them the ability to create unprivileged user namespaces by default. In this case, a profile which specified the unconfined flag and no additional permissions would be blocked from using unprivileged user namespaces. However, when combined with the userns permission above, an application confined by such a profile would then be allowed to use unprivileged user namespaces and not be confined in any other way. Whilst this does not achieve any meaningful confinement of the application, it does allow such applications to continue to use unprivileged user namespaces and avoids the risk of introducing any regression in functionality through the use of an AppArmor profile that was inadvertently too restrictive.
It is suggested that this approach will likely be the most appropriate for the majority of applications that legitimately require the use of unprivileged user namespaces, compared to a complete AppArmor profile.
Source

simon-curtis · 2024-04-30T12:51:15Z

This is very important to point out, thank you. The workaround should only be temporary and used with caution.

On the flip side, the setting kernel.apparmor_restrict_unprivileged_userns=0 is still the default for 23.10 so if you roll back then means exposing yourself to the same exploit. Risk analysis should be done.

md-owes · 2024-05-01T06:31:19Z

i forgot to provide my update that the below comment fixes the issue and is a kind of workaround. I am good to close the issue as it has unblocked my work. Thanks to all the participants in this thread especially @Spikhalskiy.

✅ I was able to solve this issue with
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
It looks like an Electron and Chromium issue electron/electron#41066 and the above workaround was originally suggested in electron/electron#41066 (comment)

yuvii · 2024-08-19T08:56:20Z

It's been 4 months. Are there any plans to resolve this issue?

MrBns · 2024-08-24T05:42:16Z

Though its works by disabling appArmor. But I don't think its a proper solution.
After 4/5 month later this issue still exist. and thats not respectable @docker

sunnn · 2024-08-26T17:11:33Z

this issue persists in Fedora 40 desktop as well

raju-gharti · 2024-08-28T21:38:41Z

When are we going to have working Docker Desktop on Ubuntu 24.04 LTS?

M00nNight · 2024-08-29T18:02:13Z

I use meta-ai to solve this error

eman1986 · 2024-09-04T02:59:30Z

I tried to avoid disabling apparmor, but I kept having issues getting virtiofsd to be accepted so I disabled apparmor until this is resolved, having docker non-functional is not an option, I've gotten along fine with apparmor not in high gear so I'll wait for someone to make a better fix.

barbariania · 2024-09-06T10:52:46Z

Actually I was able to install and can work with it

sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
Source: https://askubuntu.com/a/1512215/425896
Then I got that error (if you don't then skip 3rd step)

The following packages have unmet dependencies:
docker-desktop : Depends: docker-ce-cli but it is not installable
E: Unable to correct problems, you have held broken packages.

Add missind docker repository

sudo apt install -y ca-certificates curl gnupg lsb-release
sudo mkdir -p /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt update -y

Source: https://stackoverflow.com/a/73455413/3598880

Following the docker docs https://docs.docker.com/desktop/install/ubuntu/

kotasudhakar · 2024-09-20T05:30:57Z

I have the same problem too. The Docker engine works fine though. It just I can not open the UI.

This is the problem with the electron app itself
electron/electron#41066

hanyghorbel · 2024-09-24T22:19:55Z

you guys can check this solution here! it worked for me: https://askubuntu.com/questions/1511725/ubuntu-24-04-docker-desktop-is-not-starting#:~:text=The%20latest%20Ubuntu%2024.04%20LTS%20is%20not%20yet
the one with the title: CREATE A DEFAULT_ALLOW APPARMOR PROFILE

SickSecCo · 2024-09-26T12:31:30Z

I think this is the best solution so far: https://askubuntu.com/a/1519662/1948654

mehtachandrashekhar · 2024-09-29T10:17:36Z

https://dev.to/chandrashekhar/docker-desktop-is-not-working-on-ubuntu-2404-lts--2kpa

Read this to resolve the issue of Docker-desktop.

simon-curtis · 2024-09-29T18:51:59Z

https://dev.to/chandrashekhar/docker-desktop-is-not-working-on-ubuntu-2404-lts--2kpa

Read this to resolve the issue of Docker-desktop.

This is not the correct solution. As discussed before, this adds a blanket exception for all apps.

Please refer to the previous stack overflow comments that describe how to make docker-desktop specific exceptions

andrenatal · 2024-10-02T21:41:50Z

Same

mehtachandrashekhar · 2024-10-06T14:04:51Z

https://dev.to/chandrashekhar/docker-desktop-is-not-working-on-ubuntu-2404-lts--2kpa
Read this to resolve the issue of Docker-desktop.

This is not the correct solution. As discussed before, this adds a blanket exception for all apps.

Please refer to the previous stack overflow comments that describe how to make docker-desktop-specific exceptions

Okay, sorry for the misunderstanding. I agree with your points, as you're more senior than me.

Pianisimo · 2024-10-11T17:07:42Z

this:
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
worked for me even in distros derived from ubuntu24.04

MrBns · 2024-10-13T12:49:18Z

LOL, this issue is going over 6 month now. but still no native solution from docker. its really funny.

KatTomrushka · 2024-10-14T10:43:43Z

Thank you for your interest and patience. We want to let you know that we’re actively working on the Linux Ubuntu 24.04, and it's already in the testing phase. It’s coming soon, though we don’t have a confirmed release date just yet.

We’ll keep you updated as progress continues!

Roadmap item: docker/roadmap#655 (comment)

Praneethp07 · 2024-10-17T11:55:53Z

You can modify the /etc/sysctl.conf file or create a new configuration file under /etc/sysctl.d/ to make this change permanent. Here’s how:

Open the Sysctl Configuration: Open the sysctl configuration file with a text editor. You can use nano or any text editor of your choice:

sudo nano /etc/sysctl.conf
Add the Configuration: At the end of the file, add the following line:

kernel.apparmor_restrict_unprivileged_userns=0
Save and Exit: If using nano, press CTRL + O, then Enter to save, and CTRL + X to exit.

Reload the Sysctl Configuration: Apply the changes by reloading the sysctl settings:

sudo sysctl -p
Verify Again: Check the value again to ensure it has changed to 0:

sysctl kernel.apparmor_restrict_unprivileged_userns
Restart Docker Desktop:
After making this change permanent, restart Docker Desktop:

systemctl --user restart docker-desktop

this worked for me!

stevenlafl · 2024-10-22T14:46:09Z

Disabling this security globally is unacceptable. I've carved out an apparmor profile to unconfine Docker Desktop.

@eman1986

/etc/apparmor.d/docker-desktop:

# Docker Desktop apparmor profile to unconfine

abi <abi/4.0>,
include <tunables/global>

profile docker-desktop /opt/docker-desktop/bin/com.docker.backend flags=(unconfined) {
  userns,
}

sudo apparmor_parser -r /etc/apparmor.d/docker-desktop
systemctl --user restart docker-desktop

Do I have to mention that this does in fact work?

@KatTomrushka
Docker team, it is easy to ship an apparmor profile with your package. Just make it easy, please. A number of other software does this identical solution. This isn't something weird, it is a standard profile.

Subas-mohanty · 2024-10-23T18:42:23Z

I have used this command

$ sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
$ systemctl --user restart docker-desktop

And it worked for me, now the docker desktop app is opening, but it shows "starting the docker engine", for sometime then closes the app automatically

gzapatas · 2024-10-23T20:33:39Z

Disabling this security globally is unacceptable. I've carved out an apparmor profile to unconfine Docker Desktop.

@eman1986

/etc/apparmor.d/docker-desktop:

Docker Desktop apparmor profile to unconfine

abi <abi/4.0>,
include <tunables/global>

profile docker-desktop /opt/docker-desktop/bin/com.docker.backend flags=(unconfined) {
userns,
}
sudo apparmor_parser -r /etc/apparmor.d/docker-desktop
systemctl --user restart docker-desktop
Do I have to mention that this does in fact work?

@KatTomrushka Docker team, it is easy to ship an apparmor profile with your package. Just make it easy, please. A number of other software does this identical solution. This isn't something weird, it is a standard profile.

I confirm that this solution works perfectly. Thanks @stevenlafl

nferdica · 2024-10-25T03:20:22Z

Disabling this security globally is unacceptable. I've carved out an apparmor profile to unconfine Docker Desktop.

@eman1986

/etc/apparmor.d/docker-desktop:

Docker Desktop apparmor profile to unconfine

abi <abi/4.0>,
include <tunables/global>

profile docker-desktop /opt/docker-desktop/bin/com.docker.backend flags=(unconfined) {
userns,
}
sudo apparmor_parser -r /etc/apparmor.d/docker-desktop
systemctl --user restart docker-desktop
Do I have to mention that this does in fact work?

@KatTomrushka Docker team, it is easy to ship an apparmor profile with your package. Just make it easy, please. A number of other software does this identical solution. This isn't something weird, it is a standard profile.

Best temporary solution, thanks @stevenlafl

rimelek · 2024-10-26T09:47:51Z

It looks like Docker Desktop 4.35 now supports Ubuntu 24.04

https://docs.docker.com/desktop/install/linux/ubuntu/#prerequisites

Have an x86-64 system with Ubuntu 22.04, 24.04, or the latest non-LTS version.

I haven't tried, because I don't have Ubuntu 24.04 yet

Baloshi69 · 2024-10-26T20:45:50Z

It looks like Docker Desktop 4.35 now supports Ubuntu 24.04

https://docs.docker.com/desktop/install/linux/ubuntu/#prerequisites

Have an x86-64 system with Ubuntu 22.04, 24.04, or the latest non-LTS version.

I haven't tried, because I don't have Ubuntu 24.04 yet

Was just waiting for ... it just make my day trying to use pennaylaneai lighting-gpu with nvidia within ubuntu24 and it was not workng at all.

will remove it and install it again with new instruciton let see

rimelek · 2024-10-26T20:50:49Z

@Baloshi69 Only Docker Desktop for Windows supports NVIDIA GPUs when using the WSL2 backend, because WSL2 supports NVIDIA GPUs. On Linux you will need Docker CE for using GPUs.

https://docs.docker.com/engine/install/ubuntu/

nferdica · 2024-10-28T03:02:58Z

@md-owes After the update on the 24th of this month, I believe the problem was resolved, I tested it on two devices and it worked perfectly. I think the topic can now be closed! 🎉

https://docs.docker.com/desktop/release-notes/

MihaelaStoica · 2024-10-28T10:58:54Z

Resolving this issue, as we had added support for Ubuntu 24.04 in Docker Desktop 4.35.0.
See release note.

juanctj · 2024-12-15T18:03:24Z

You can modify the /etc/sysctl.conf file or create a new configuration file under /etc/sysctl.d/ to make this change permanent. Here’s how:

Open the Sysctl Configuration: Open the sysctl configuration file with a text editor. You can use nano or any text editor of your choice:

sudo nano /etc/sysctl.conf Add the Configuration: At the end of the file, add the following line:

kernel.apparmor_restrict_unprivileged_userns=0 Save and Exit: If using nano, press CTRL + O, then Enter to save, and CTRL + X to exit.

Reload the Sysctl Configuration: Apply the changes by reloading the sysctl settings:

sudo sysctl -p Verify Again: Check the value again to ensure it has changed to 0:

sysctl kernel.apparmor_restrict_unprivileged_userns Restart Docker Desktop: After making this change permanent, restart Docker Desktop:

systemctl --user restart docker-desktop

this worked for me!

It´s work for me, thanks!!!!

md-owes added the needs-triage label Apr 27, 2024

Spikhalskiy mentioned this issue Apr 29, 2024

Ubuntu 24.04 Beta LTS - Docker Desktop not starting after install Joshua-Riek/ubuntu-rockchip#735

Open

MihaelaStoica closed this as completed Oct 28, 2024

CristianArean mentioned this issue Oct 31, 2024

Mention that ubuntu 24.04 lts is not fully supported docker/docs#21304

Closed

1 task

Docker desktop stopped working after upgrading Ubuntu from 23.10 to 24.04 #209

Docker desktop stopped working after upgrading Ubuntu from 23.10 to 24.04 #209

Comments

md-owes commented Apr 27, 2024

Description

Reproduce

Expected behavior

docker version

docker info

Diagnostics ID

Additional Info

andinianst93 commented Apr 27, 2024

wgrs commented Apr 27, 2024 • edited Loading

luiz-fernandoalves commented Apr 28, 2024 • edited Loading

raza2022 commented Apr 28, 2024

serious-angel commented Apr 28, 2024 • edited Loading

beelzick commented Apr 28, 2024

md-owes commented Apr 29, 2024

ptdatta commented Apr 29, 2024

vic-reis commented Apr 29, 2024

Arnispl commented Apr 29, 2024

Lapakin commented Apr 29, 2024

mayurDayal2000 commented Apr 29, 2024 • edited Loading

serious-angel commented Apr 29, 2024 • edited Loading

ptdatta commented Apr 29, 2024 • edited Loading

simon-curtis commented Apr 29, 2024 • edited Loading

Spikhalskiy commented Apr 29, 2024 • edited Loading

Spikhalskiy commented Apr 29, 2024 • edited Loading

simon-curtis commented Apr 29, 2024 • edited Loading

serious-angel commented Apr 29, 2024

sebasalas commented Apr 29, 2024

ptdatta commented Apr 30, 2024

luiz-fernandoalves commented Apr 30, 2024

tuberquia2115 commented Apr 30, 2024

luiz-fernandoalves commented Apr 30, 2024 • edited Loading

kartikeya-lyzr commented Apr 30, 2024

serious-angel commented Apr 30, 2024 • edited Loading

simon-curtis commented Apr 30, 2024

md-owes commented May 1, 2024

yuvii commented Aug 19, 2024

MrBns commented Aug 24, 2024

sunnn commented Aug 26, 2024

raju-gharti commented Aug 28, 2024

M00nNight commented Aug 29, 2024

eman1986 commented Sep 4, 2024

barbariania commented Sep 6, 2024

kotasudhakar commented Sep 20, 2024

hanyghorbel commented Sep 24, 2024

SickSecCo commented Sep 26, 2024 • edited Loading

mehtachandrashekhar commented Sep 29, 2024

simon-curtis commented Sep 29, 2024

andrenatal commented Oct 2, 2024

mehtachandrashekhar commented Oct 6, 2024

Pianisimo commented Oct 11, 2024

MrBns commented Oct 13, 2024

KatTomrushka commented Oct 14, 2024

Praneethp07 commented Oct 17, 2024

stevenlafl commented Oct 22, 2024 • edited Loading

Subas-mohanty commented Oct 23, 2024

gzapatas commented Oct 23, 2024

Docker Desktop apparmor profile to unconfine

nferdica commented Oct 25, 2024

Docker Desktop apparmor profile to unconfine

rimelek commented Oct 26, 2024

Baloshi69 commented Oct 26, 2024

rimelek commented Oct 26, 2024

nferdica commented Oct 28, 2024

MihaelaStoica commented Oct 28, 2024

juanctj commented Dec 15, 2024

wgrs commented Apr 27, 2024 •

edited

Loading

luiz-fernandoalves commented Apr 28, 2024 •

edited

Loading

serious-angel commented Apr 28, 2024 •

edited

Loading

mayurDayal2000 commented Apr 29, 2024 •

edited

Loading

serious-angel commented Apr 29, 2024 •

edited

Loading

ptdatta commented Apr 29, 2024 •

edited

Loading

simon-curtis commented Apr 29, 2024 •

edited

Loading

Spikhalskiy commented Apr 29, 2024 •

edited

Loading

Spikhalskiy commented Apr 29, 2024 •

edited

Loading

simon-curtis commented Apr 29, 2024 •

edited

Loading

luiz-fernandoalves commented Apr 30, 2024 •

edited

Loading

serious-angel commented Apr 30, 2024 •

edited

Loading

SickSecCo commented Sep 26, 2024 •

edited

Loading

stevenlafl commented Oct 22, 2024 •

edited

Loading