[Bug] Install Fails With Local Network Sharing Disabled In VPN

[microsoftruinseverything456]

What version of WinBoat are you running?

0.8.5

Your Environment

Arch Linux (CachyOS) Mullvad VPN

Steps to Reproduce / Context

Install Winboat with Mullvad VPN on default settings. Docker container isn't created for Winboat.

Logs

❯ docker logs winboat Error response from daemon: No such container: winboat

❯ docker compose down docker compose up -d no configuration file provided: not found no configuration file provided: not found

❯ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

Expected Behavior

Apps that utilize local ports normally work fine without granting access to the local network itself (i.e. other devices within the actual, non-VPN network). Not sure why it's an issue here.

Current Behavior

Currently fixed after enabling local network sharing. However, this is not preferred due to the greater potential for tracking, exploits, and network surveillance by less secure devices within the same network. Winboat notably cannot detect local devices itself after some limited testing.

Possible Solution

At this time, enable local network sharing in VPN settings.

Quality Notice

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

[sprinteroz]

I would run the VPN in Linux for several reasons:

You're running a container - There's inherent latency with containerized Windows, so adding VPN overhead inside the VM compounds the performance impact Resource efficiency - Your system resources might already be limited running WinBoat Firewall considerations - Are you using a firewall like SimpleWall to reduce unnecessary Windows traffic? Running the VPN in Linux means your firewall rules work more effectively Router-level VPN is even better - Running the VPN on your router protects your entire network and eliminates any per-device overhead Resource allocation issues - You might have given WinBoat too much or too little resources, affecting VPN performance inside the container

Bottom line: Running VPN in Linux (or your router) keeps the VPN overhead outside the Windows container, giving you better performance and simpler network management.

[microsoftruinseverything456]

@sprinteroz No VPN was running in the VM. This is due to the Linux VPN's disabled local network sharing causing interference with the local server created by Winboat. All of the issues mentioned occurred during installation or startup of the VM with nothing custom installed on Windows.