rogueco
commented
4 months ago I'm having the same issue
Open FlexLV opened 4 months ago
rogueco
commented
4 months ago I'm having the same issue
YoEight
commented
4 months ago I have the same issue with Docker Desktop not working on Ubuntu 24.04 but it reports that application has lost its connection with Xwayland instead.
darkjackx
commented
4 months ago I just installed docker desktop with Ubuntu 24.04 LTS
sudo apt-get update sudo apt-get install ca-certificates curl sudo install -m 0755 -d /etc/apt/keyrings sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc sudo chmod a+r /etc/apt/keyrings/docker.asc
echo \ "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \ $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \ sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update
run sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
run sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 systemctl --user restart docker-desktop
s-andrzejewski
commented
4 months ago @darkjackx Awesome! You help me a lot. Thanks! ❤️🔥
gregpalaci
commented
3 months ago I have the same issue with Docker Desktop not working on Ubuntu 24.04 but it reports that application has lost its connection with Xwayland instead.
I'm using X11 with 24.04 think it isn't the issue
UPDATE https://github.com/docker/desktop-linux/issues/211#issuecomment-2097555794 works
make sure to run commands one by one and think there is a white space issue with the docker.list generation
adjusted:
deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu
noble stable
``` to
deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu noble stable
But big thanks! 
freemvmt
commented
3 months ago Anyone got the lead on a way to get Docker Desktop running with the new security defaults in Ubuntu 24.04?
From what I've read in the release notes and in the AppArmor docs, this should be a case of making a profile for Docker Desktop in /etc/apparmor.d.
I tried doing this, by adding /etc/apparmor.d/opt.docker-desktop.bin.docker-desktop (named in accordance with the docs), with the following contents:
# This profile allows everything and only exists to give the
# application a name instead of having the label "unconfined"
abi <abi/4.0>,
include <tunables/global>
profile docker-desktop /opt/docker-desktop/bin/docker-desktop flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists <local/chrome>
}This is essentially a copy-paste job from the chrome profile given as an example in the release notes.
I then attempted to parse this profile into the kernel and reload the whole apparmor thing...
sudo apparmor_parser -r /etc/apparmor.d/opt.docker-desktop.bin.docker-desktop
sudo systemctl reload apparmor.serviceAfter all this, Docker Desktop does boot up! But then gets stuck on the following screen:
Looking at the kernel log (sudo dmesg), I can see that it hit a trap:
[30582.754989] traps: Docker Desktop[49878] trap int3 ip:614d07488ad1 sp:7fff090163c0 error:0 in Docker Desktop[614d0386f000+800a000]My guess is that I need to unconfine some other binaries which docker-desktop is drawing on, but I've run out of steam now so am wondering whether anyone else has made progress?
gregpalaci
commented
3 months ago @freemvmt I haven't used apparmor but think you want to look at this thread https://github.com/moby/moby/issues/33060#issuecomment-1698935183 you probably need "docker-default" profile
Sr-santi
commented
3 months ago thanks @darkjackx i forgot to execute some commands during my installation process
hoipranav
commented
3 weeks ago @darkjackx thanks it worked!!
Description
I followed the Docker documentation step-by-step and successfully installed Docker. However, issues began to arise when I attempted to install Docker Desktop. Initially, Docker Desktop opened with an error, and since then, it hasn't opened at all. Despite trying various commands, installing other packages, and running it through the terminal, it only runs partially and continuously displays a message saying "waiting for Docker engine to start," even though the Docker engine has already started. Now I'm stuck. I ran diagnostics, and the results indicate that the Linux VM isn't running and the Docker engine hasn't started, although it is already running. I also tried reinstalling using deb installation
Reproduce
for pkg in docker.io docker-doc docker-compose docker-compose-v2 podman-docker containerd runc; do sudo apt-get remove $pkg; done
Add Docker's official GPG key:
sudo apt-get update sudo apt-get install ca-certificates curl sudo install -m 0755 -d /etc/apt/keyrings sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc sudo chmod a+r /etc/apt/keyrings/docker.asc
Add the repository to Apt sources:
echo \ "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \ $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \ sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo docker run hello-world
(it runned fine)
modprobe kvm modprobe kvm_intel # Intel processors kvm-ok sudo usermod -aG kvm $USER
Expected behavior
No response
docker version
docker info
Diagnostics ID
6F8D0A05-7112-4532-AE33-AECB3813A45D/20240503095028
Additional Info
No response