Skip to content

[Bug] "services.windows.volumes.3 must be a string" prevents container and guest API from restarting #779

@JamesKulrich

Description

@JamesKulrich

What version of WinBoat are you running?

0.9.0

Your Environment

--- System Info ---
Operating System: Fedora Linux 43
KDE Plasma Version: 6.6.4
KDE Frameworks Version: 6.26.0
Qt Version: 6.10.3
Kernel Version: 7.0.8-100.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: AMD Radeon RX 6650 XT
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C56
System Version: 2.0

Steps to Reproduce / Context

Winboat will create an environment, but will refuse to restart once it has been closed once.

  1. Install Winboat v0.9.0 (via .rpm package)
  2. Go through the setup (I tried several versions of Windows 10 and 11 - I don't think it matters)
  3. Stop the container
  4. Attempt to launch the container

Logs

container.log
install.log
winboat.log

Expected Behavior

This command should work as intended:
docker compose -f /home/james/.winboat/docker-compose.yml up -d

Current Behavior

This pops up within container.log:
2026-05-17 18:23:08 | ERROR | Failed to run compose command 'docker compose -f /home/james/.winboat/docker-compose.yml up -d'

2026-05-17 18:23:08 | ERROR | Error: Command failed: docker compose -f /home/james/.winboat/docker-compose.yml up -d

validating /home/james/.winboat/docker-compose.yml: services.windows.volumes.3 must be a string

This line seems to get repeated forever:
2026-05-17 18:23:09 | ERROR | Failed to get status of docker container Error: Command failed: docker inspect --format={{.State.Status}} WinBoat error: no such object: WinBoat

Possible Solution

I think I found a fix within docker-compose.yml; an extra "-" gets added within the volumes section which docker compose apparently doesn't like. Deleting this seems to let the container and guest API start as they should.

Image

Quality Notice

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingneeds-triageAn issue that is to be reviewed and assessed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions