-
-
Notifications
You must be signed in to change notification settings - Fork 384
Description
What version of WinBoat are you running?
0.8.7
Your Environment
Linux distro used: Ubuntu 24.04.3 LTS
Desktop Environment used: LXQt 1.4.0
FreeRDP: flatpak 3.17.2
xrdp: 0.9.24-4
Steps to Reproduce / Context
Install WinBoat from a deb packet.
Run WinBoat from the context menu.
Proceed to the step when "WinBoat is now installing Windows. Please be patient..."
Logs
~/.winboat/install.log
545ccfce83e1 Extracting [==================================================>] 136B/136B
545ccfce83e1 Extracting [==================================================>] 136B/136B
545ccfce83e1 Pull complete
windows Pulled
Network winboat_default Creating
Network winboat_default Created
Container WinBoat Creating
Container WinBoat Created
Container WinBoat Starting
Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint WinBoat (3b6c8915eef3b3fa3314cb141cea98df8456c9ef7a56acdd59e7b19ec30c8052): failed to bind host port for 0.0.0.0:3389:172.18.0.2:3389/tcp: address already in use
Expected Behavior
Installation finishes successfully.
Current Behavior
An error occurred while installing Windows. Please check the logs in ~/.winboat and verify docker logs WinBoat in your terminal for more information. To reset and try again, follow these instructions.
Possible Solution
Solution 1. Add additional check into "Pre-Requisites" window.
Solution 2. Update documentation to include a check whether port 3389 is already in use by any other software
Solution 3. Allow custom port instead of 3389
Quality Notice
- I have checked the issue tracker and verified that this bug is a unique case.
