Answers: <p><strong>Step-1:</strong> Fix chrome-sandbox permissions, which break the start of docker desktop</p>
  <pre><code>sudo chmod 4755 /opt/docker-desktop/chrome-sandbox
  </code></pre>
  <p><strong>Step-2:</strong> The latest Ubuntu 24.04 LTS is not yet supported by docker-desktop. Docker Desktop will fail to start. Due to a change in how the latest Ubuntu release restricts the unprivileged namespaces.
  Run the following command at least once (in my case, I must run the command, then restart and rerun the command):</p>
  <pre><code>sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
  </code></pre>
  
Answers: CC BY-SA 4.0
Answers: 2024-09-22T16:34:31.673Z
Answers: 2024-09-23T04:35:50.507Z
Answers: 2024-09-23T04:35:50.507Z
Answers: klaucode
Body: <p>after recommendation from Ubuntu I upgraded to newer version Ubuntu-24.04. Upgrade finished without any errors. After upgrade, docker from the terminal is working without any problems, but I'm unable to start docker-desktop.</p>
  <p>I totally uninstalled and cleaned docker-desktop and docker with all relevant folders docker and installed it again. But it didn't helped. Docker is running and I'm able to use it, but docker-desktop unable to start.</p>
  <p>Then I run diagnostics: <code>/opt/docker-desktop/bin/com.docker.diagnose gather</code>.</p>
  <p>In <code>dmesg.err.txt</code> I found following error: <code>dmesg: read kernel buffer failed: Operation not permitted</code>.</p>
  
Comments: CC BY-SA 4.0
Comments: 2024-09-19T19:18:33.573Z
Comments: in path ~/.docker/desktop/log/host/Docker Desktop.stderr.log I found an error: `The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/docker-desktop/chrome-sandbox is owned by root and has mode 4755.`. I set permissions by recommendation, Docker Desktop is now starting, but It will freeze on loading screen: `docker engine is the underlying technology that runs containers`. I don't know now, if it's next issue, or issue related with previous issue.
Comments: klaucode
Tags: <docker>
Title: Unable to start Docker Desktop after upgrade to Ubuntu 24.04
UserDisplayName: klaucode
ThreadText: # Unable to start Docker Desktop after upgrade to Ubuntu 24.04
  
  (Asked by: username_0 on 2024-09-19)
  
  after recommendation from Ubuntu I upgraded to newer version Ubuntu-24.04. Upgrade finished without any errors. After upgrade, docker from the terminal is working without any problems, but I'm unable to start docker-desktop.
  
  I totally uninstalled and cleaned docker-desktop and docker with all relevant folders docker and installed it again. But it didn't helped. Docker is running and I'm able to use it, but docker-desktop unable to start.
  
  Then I run diagnostics: `/opt/docker-desktop/bin/com.docker.diagnose gather`.
  
  In `dmesg.err.txt` I found following error: `dmesg: read kernel buffer failed: Operation not permitted`.
  
  **Tags:** docker
  
  > **Comments:**
  > **username_0**: in path ~/.docker/desktop/log/host/Docker Desktop.stderr.log I found an error: `The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/docker-desktop/chrome-sandbox is owned by root and has mode 4755.`. I set permissions by recommendation, Docker Desktop is now starting, but It will freeze on loading screen: `docker engine is the underlying technology that runs containers`. I don't know now, if it's next issue, or issue related with previous issue.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2024-09-22. Score: 0
  
  **Step-1:** Fix chrome-sandbox permissions, which break the start of docker desktop
  
  ```
  sudo chmod 4755 /opt/docker-desktop/chrome-sandbox
  
  ```
  
  **Step-2:** The latest Ubuntu 24.04 LTS is not yet supported by docker-desktop. Docker Desktop will fail to start. Due to a change in how the latest Ubuntu release restricts the unprivileged namespaces.
  Run the following command at least once (in my case, I must run the command, then restart and rerun the command):
  
  ```
  sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
  
  ```
  
  
  ---
  
  