[Bug] WinBoat Guest API Occasionally Doesn't Run

[ourichermath]

What version of WinBoat are you running?

0.9.0 as an Appimage on Bazzite w/ KDE Plasma (i.e., Podman)

Your Environment

Operating System: Bazzite 43
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.17.7-ba22.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 9070 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B550 VISION D-P
System Version: -CF

Steps to Reproduce / Context

This seems random. Occasionally, I'll go to WinBoat to start up my Windows 11 Pro container and the WinBoat Guest API will remain Offline. The Container will start, but not the Guest API. My only workaround when that happens is to restart the computer. After that, everything will start normally until the next random occurrence.

Logs

container.log
install.log
winboat.log

and here's a link to my latest boot log, just in case it's related to:

#617

https://paste.centos.org/view/d2f08187

Expected Behavior

When clicking on the Winboat Start icon (green "play" triangle to the right of the WinBoat HOME tab), both the WinBoat Guest API and the Container should start running.

Current Behavior

Occasionally, clicking the Start icon will start only the Container and not the WinBoat Guest API. I think that when this happens, the container.log file contains:

2026-01-03 01:16:25 | ERROR | Failed to run container action 'podman  container  start  WinBoat'
2026-01-03 01:16:25 | ERROR | Error: Command failed: podman container start WinBoat
Error: unable to start container "713d4c1c21b0b5d303d02fc038a0dd3e3c7cebaff27fe3491bf95b4c559a0da2": crun: cannot stat `/dev/bus/usb/001/004`: No such file or directory: OCI runtime attempted to invoke a command that was not found

and the winboat.log file contains:

2026-01-03 01:16:25 | ERROR | There was an error performing the container action.
2026-01-03 01:16:25 | ERROR | Error: Command failed: podman container start WinBoat
Error: unable to start container "713d4c1c21b0b5d303d02fc038a0dd3e3c7cebaff27fe3491bf95b4c559a0da2": crun: cannot stat `/dev/bus/usb/001/004`: No such file or directory: OCI runtime attempted to invoke a command that was not found

Possible Solution

No response

Quality Notice

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

[donCESAR12345]

I'm having this same issue, in my case it was asking for /usb/003/002, a quick ls in /dev/bus/usb/003 showed that these are USB devices connected such as external HDDs, mouse dongles, etc. In my case I did have the 001, 004, 005, 006, and then the rest were dynamically loaded with a new number, that is, if I disconnected a USB device and changed its port, it generated a new number, but never replacing an old one, such as the required one for WinBoat.

After a quick restart, it was now asking for the /usb/004/004, I only had up to 003, but then I connected an external HDD and now it was working correctly, container started up right away, I didn't even had to mount it, just connect it to have the /usb/004/004 device listed.

My Environment
Operating System: Arch Linux
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.18.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 32 GiB of RAM (31.1 GiB usable)
Graphics Processor: Intel® Iris® Xe Graphics
Manufacturer: HP
Product Name: HP Pavilion Laptop 15-eg0xxx