-
-
Notifications
You must be signed in to change notification settings - Fork 516
Closed
Labels
bugSomething isn't workingSomething isn't workingneeds-triageAn issue that is to be reviewed and assessedAn issue that is to be reviewed and assessed
Description
What version of WinBoat are you running?
0.8.7
Your Environment
Linux Distribution: Linux Mint 22.1 Cinnamon
Docker version: 28.5.1
Default browser: Librewolf 143.0.4-1
I have also tried using Firefox and Chromium as my default browser.
Steps to Reproduce / Context
- Download the .deb file from https://www.winboat.app/.
- Install the .deb file
- Make sure all the pre-requisites are met.
- Proceed with installation, Windows 11 pro.
- Installation fails.
I have also tried using the .AppImage, but the same error occurs.
Logs
install.log
[...]
2025-10-14 07:23:24 | INFO | Starting container...
2025-10-14 07:23:24 | ERROR | Container WinBoat Creating
Container WinBoat Created
Container WinBoat Starting
Container WinBoat Started
2025-10-14 07:23:24 | INFO | Container started successfully.
2025-10-14 07:23:27 | INFO | New state: "Monitoring Preinstall"
2025-10-14 07:23:27 | INFO | Starting preinstall monitoring...
2025-10-14 07:23:27 | ERROR | Error monitoring container: FetchError: request to http://127.0.0.1:8006/msg.html failed, reason: connect ECONNREFUSED 127.0.0.1:8006
2025-10-14 07:23:27 | INFO | New state: "Install Error"
winboat.log
2025-10-14 07:43:16 | INFO | Winboat Container state changed to running
2025-10-14 07:43:16 | INFO | Creating Winboat API intervals...
2025-10-14 07:43:16 | INFO | Winboat Container state changed to restarting
2025-10-14 07:43:16 | INFO | Destroying Winboat API intervals...
Expected Behavior
The program should continue with the installation.
Current Behavior
- An error occurs while installing windows.
- Browser is unable to check the status.
Possible Solution
I do not know of a possible solution. I've seen that #312 is also unable to install, but gets different log errors. Their error seems to be creating the docker container, while mine seems to be about monitoring that container.
Both of us are using a Debian based distro, so I think the issue might be there.
Quality Notice
- I have checked the issue tracker and verified that this bug is a unique case.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingneeds-triageAn issue that is to be reviewed and assessedAn issue that is to be reviewed and assessed