Docker (Rancher Desktop) not working on Linux

[salimbouch]

Expected behavior

As an IDEasy user, I want to be able to use rancher desktop on linux.

Actual behavior

after starting this tool, IDEasy throws an error.

Steps to reproduce (bug) / Use Case of feature request (enhancement)

1. ide docker

Comments/Hints:

saboucha@CE66616:~/projects/newProject$ ide docker
Updates are available for the settings repository. If you want to pull the latest changes, call ide update.
We need to run the following privileged command(s):
curl -s https://download.opensuse.org/repositories/isv:/Rancher:/stable/deb/Release.key | gpg --dearmor | sudo dd status=none of=/usr/share/keyrings/isv-rancher-stable-archive-keyring.gpg
echo 'deb [signed-by=/usr/share/keyrings/isv-rancher-stable-archive-keyring.gpg] https://download.opensuse.org/repositories/isv:/Rancher:/stable/deb/ ./' | sudo dd status=none of=/etc/apt/sources.list.d/isv-rancher-stable.list
sudo apt update
sudo apt install -y --allow-downgrades rancher-desktop=1.16.0*
This will require root permissions!
[sudo] password for saboucha:
Hit:1 http://archive.ubuntu.com/ubuntu noble InRelease
Get:2 http://archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
Hit:3 https://download.opensuse.org/repositories/isv:/Rancher:/stable/deb ./ InRelease
Get:4 http://archive.ubuntu.com/ubuntu noble-backports InRelease [126 kB]
Get:5 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages [675 kB]
Get:6 http://security.ubuntu.com/ubuntu noble-security InRelease [126 kB]
Get:7 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Components [132 kB]
Get:8 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages [722 kB]
Get:9 http://security.ubuntu.com/ubuntu noble-security/main amd64 Components [7188 B]
Get:10 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 Components [310 kB]
Get:11 http://archive.ubuntu.com/ubuntu noble-updates/restricted amd64 Components [212 B]
Get:12 http://archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 Components [940 B]
Get:13 http://archive.ubuntu.com/ubuntu noble-backports/main amd64 Components [208 B]
Get:14 http://archive.ubuntu.com/ubuntu noble-backports/universe amd64 Components [11.7 kB]
Get:15 http://archive.ubuntu.com/ubuntu noble-backports/restricted amd64 Components [212 B]
Get:16 http://archive.ubuntu.com/ubuntu noble-backports/multiverse amd64 Components [212 B]
Get:17 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Components [51.9 kB]
Get:18 http://security.ubuntu.com/ubuntu noble-security/restricted amd64 Components [212 B]
Get:19 http://security.ubuntu.com/ubuntu noble-security/multiverse amd64 Components [212 B]
Fetched 2290 kB in 1s (1528 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
56 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
rancher-desktop is already the newest version (1.16.0-2.1).
Selected version '1.16.0-2.1' (isv:Rancher:stable:download.opensuse.org [amd64]) for 'rancher-desktop'
0 upgraded, 0 newly installed, 0 to remove and 56 not upgraded.
MESA: error: ZINK: failed to choose pdev
glx: failed to create drisw screen
Internal error: Undefined error handling THROW_CLI
Running command '/usr/bin/rancher-desktop'
failed with exit code 133!
Running command '/usr/bin/rancher-desktop'
failed with exit code 133!

Error: IDEasy failed with exit code 133

Affected version:

• OS: Linux (tested on Ubuntu 24.04.1 LTS
• IDEasy: 2024.12.001-beta-SNAPSHOT

[hohwille]

IMHO this issue is invalid as it looks to me it was tested on Ubuntu in WSL of Windows.
Please be aware that here Ubuntu already runs in WSL what is a virtualization environment that has limitations.
Docker itself is also a virtualization environment so you are somehow nesting VMs.
Windows users need to operate Docker on their host.
If you need docker support for Linux, you need to run Linux as host OS.

I tried it on my OpenSUSE tumbleweed and it worked.
However, I found and filed #950 during my test.
To double-check someone who has Ubuntu installed as Host OS could retest this and verify it is working.
If so, we can close this as invalid.