Command failed: docker container start WinBoat -> ventoy ("Winboat Guest Api offline - Container exiting")

Open Erik-38 opened this issue 3 months ago • 1 comments

What version of WinBoat are you running?

0.8.7-x86_64.AppImage

Your Environment

Linux Mint Cinnamon (Zara) Prozessor AMD Ryzen 5 5600G with Radeon Graphics, 3901 MHz, 6 Kern(e), 12 logische(r) Prozessor(en) Mainboard A520M DS3H (Gigabyte Technology Co) BIOS-Version/-Datum American Megatrends International, LLC. F20g, 11.03.2025

Steps to Reproduce / Context

I got WinBoat up and running (as a layman) on my Linux Mint computer (Cinnamon/Zara) without any major problems. After installation, I was able to start, pause, stop, exit, and restart WinBoat. It worked flawlessly.

After restarting the computer, Winboat remained stuck for several minutes with the message “Winboat Guest Api offline - Container exiting.” Even after reinstalling WinBoat, the problem persisted. I found the following note in the log file: “error mounting ”/media/username/Ventoy1/OS_Windows/Windows_10_x64_PT.iso" (excerpt from the complete log, see below).

I don't know if and how the problem with Ventoy is related to Winboat. I have a USB stick with Ventoy for testing and installing different operating systems. However, I can't remember whether I installed the computer on which the described problem occurred using Ventoy. I am reporting the problem and the note from the log in the hope that it will be helpful in troubleshooting and improving WinBoat.

Logs

************** Winboat.log ********************

2025-09-13 00:25:54 | INFO | Successfully stopped WinBoat container 2025-09-13 00:25:54 | INFO | Winboat Container state changed to exited 2025-09-13 00:25:54 | INFO | Destroying Winboat API intervals... 2025-09-13 00:26:10 | INFO | Starting WinBoat container... 2025-09-13 00:26:10 | ERROR | There was an error performing the container action. 2025-09-13 00:26:10 | ERROR | Command failed: docker container start WinBoat Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/media/username/Ventoy1/OS_Windows/Windows_10_x64_PT.iso" to rootfs at "/boot.iso": create mountpoint for /boot.iso mount: cannot create subdirectories in "/var/lib/docker/overlay2/9a0700986452f6509e2b835629ee5d8def34e875be52e023576daccefc53f52b/merged/boot.iso": not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type Error: failed to start containers: WinBoat

2025-09-14 23:33:46 | INFO | Starting WinBoat container... 2025-09-14 23:33:46 | ERROR | There was an error performing the container action. 2025-09-14 23:33:46 | ERROR | Command failed: docker container start WinBoat Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/media/username/Ventoy1/OS_Windows/Windows_10_x64_PT.iso" to rootfs at "/boot.iso": create mountpoint for /boot.iso mount: cannot create subdirectories in "/var/lib/docker/overlay2/9a0700986452f6509e2b835629ee5d8def34e875be52e023576daccefc53f52b/merged/boot.iso": not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type Error: failed to start containers: WinBoat

2025-09-14 23:50:54 | INFO | Starting WinBoat container... 2025-09-14 23:50:54 | ERROR | There was an error performing the container action. 2025-09-14 23:50:54 | ERROR | Command failed: docker container start WinBoat Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/media/username/Ventoy1/OS_Windows/Windows_10_x64_PT.iso" to rootfs at "/boot.iso": create mountpoint for /boot.iso mount: cannot create subdirectories in "/var/lib/docker/overlay2/9a0700986452f6509e2b835629ee5d8def34e875be52e023576daccefc53f52b/merged/boot.iso": not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type Error: failed to start containers: WinBoat

2025-09-16 21:11:07 | INFO | Starting WinBoat container... 2025-09-16 21:11:07 | ERROR | There was an error performing the container action. 2025-09-16 21:11:07 | ERROR | Command failed: docker container start WinBoat Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/media/username/Ventoy1/OS_Windows/Windows_10_x64_PT.iso" to rootfs at "/boot.iso": create mountpoint for /boot.iso mount: cannot create subdirectories in "/var/lib/docker/overlay2/9a0700986452f6509e2b835629ee5d8def34e875be52e023576daccefc53f52b/merged/boot.iso": not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type Error: failed to start containers: WinBoat

Expected Behavior

winboat should also work after restarting the PC

Current Behavior

After restarting the computer, the newly installed and functioning Winboat installation no longer starts (error message: Winboat Guest API offline - Container exiting.)

Possible Solution

No response

Quality Notice

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

Oct 16 '25 14:10 Erik-38

I also get the same problem. My workaround:

Edit ~/.winboat/docker-compose.yaml by deleting the - "/media/username/Ventoy1/OS_Windows/Windows_10_x64_PT.iso:/boot.iso" line
Recreate the container by running command docker-compose up in ~/.winboat directory
After the docker-compose up done, close it by typing Ctrl+C
Reopen the WinBoat App and press Start. It should be running normal again

Nov 10 '25 07:11 arfaiz33