docker not detected

[GyomeiHimejima9906]

What version of WinBoat are you running?

0.8.7

Your Environment

Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.5-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 20 × Intel® Core™ i5-14600KF
Memory: 32 GiB of RAM (31.1 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3060
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D98
System Version: 3.0
FreeRDP 3.x.x

P.S: docker in installed and I can run somethink with docker with terminal/docker compose and run docker ps

gbcosner@fedora:~$ docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES

gbcosner@fedora:~$ getent group docker
docker:x:971:root,gbcosner
gbcosner@fedora:~$ 

Steps to Reproduce / Context

1. install
2. configure
3. see errore

Logs

appUsage.json
install.log
winboat.config.json
winboat.log

Expected Behavior

to be able to install

Current Behavior

unable to configure and install windows due docker error

Possible Solution

No response

Quality Notice

• I have checked the issue tracker and verified that this bug is a unique case.

[Jagholin]

As it clearly says in the window, you have to add your user to the docker group:

usermod -aG docker $USER

(you might need to create docker group first)

Also, you need to activate docker daemon in SystemD(it doesn't do it automatically):

systemctl enable docker.service
systemctl enable containerd.service

(the service may be named differently)

Also see https://docs.docker.com/engine/install/linux-postinstall/

[Levev]

Also if you're using the AppImage version, try running it with --no-sandbox

[GyomeiHimejima9906]

Inoltre, se stai utilizzando la versione AppImage, prova a eseguirla con --no-sandbox

sorry but using rpm

[GyomeiHimejima9906]

as you can see in the screenshot i have already done all docker instruction and rebooted

[ben-mcginty]

I just want to chime in and say that I am also getting this error and have docker installed and added myself to the docker group. I doubt having other docker containers running at the same time would cause an issue, but you never know.
I'm also on Fedora 43 KDE and am up-to-date on all my packages.

[Ash-Olorenshaw]

I can confirm that this is the same issue I'm facing, but on Fedora 42; my user is in the 'docker' group and the 'hello-world' container works fine. I have installed and reinstalled 3 times now but the problem persists. If it helps, I find running

docker info

bizarrely always reports that Docker engine isn't running despite it being available.

[ben-mcginty]

Mine seemed to fix itself after restarting. Not sure what happened or why it was fixed but it works. I've enabled it as a startup service as done by the docker docs. I'm running F43 so idk.

[Ash-Olorenshaw]

Mine seemed to fix itself after restarting. Not sure what happened or why it was fixed but it works. I've enabled it as a startup service as done by the docker docs. I'm running F43 so idk.

I wished that worked for me, restarting did not work. Maybe I'll need to upgrade to F43

[Ash-Olorenshaw]

Ok, I have found the resolution to the issue for me. Due to my work I have to run Docker Desktop and Docker, I switched instead to PodMan desktop and reinstalled Docker entirely just with the docker-cli package. However, docker info (which I imagine is how WinBoat detects if Docker is running; I haven't looked in the codebase yet) will report that Docker isn't running if Docker engine is running but Docker Desktop is not.

The way I ended up fixing this was first uninstalling everything related to Docker, then installing just Docker CLI. After that, I deleted ~/.docker which holds your Docker configurations (back up if you need to). And voila! Suddenly, both Winboat and docker info will correctly report that Docker is running!