[Bug] Docker Compose (Snap) Cannot Access ~/.winboat/ Due to Confinement

[lancer-code]

What version of WinBoat are you running?

WinBoat 0.8.7

Your Environment

Operating System: Ubuntu 24.04 LTS Desktop Environment: GNOME Docker Version: Docker Compose v2.33.1 (installed via Snap) Installation Method: System package (deb/rpm) FreeRDP Version: 3.17 (issue occurs before FreeRDP is used)

Steps to Reproduce / Context

1. Install WinBoat on Ubuntu 24.04
2. Install Docker Compose via Snap: sudo snap install docker
3. Launch WinBoat application
4. Configure Windows 11 VM with default settings (4GB RAM, 2 CPU cores, 32GB disk)
5. Click "Start Installation" or attempt to start the container

Logs

2025-10-14 21:52:11 | ERROR | Failed to start container.
2025-10-14 21:52:11 | ERROR | Error: Command failed: docker compose -f /home/usr/.winboat/docker-compose.yml up -d
open /home/user/.winboat/docker-compose.yml: permission denied

### Expected Behavior

WinBoat should successfully create and start the Windows VM container using the docker-compose.yml file in `~/.winboat/` directory.

### Current Behavior

The installation fails with a permission denied error

### Possible Solution

### Solution 1: Use Non-Hidden Directory (Workaround - Confirmed Working)
Move the configuration to a non-hidden directory:
```bash
mkdir ~/winboat-config
cp -r ~/.winboat/* ~/winboat-config/
# Update WinBoat to use ~/winboat-config/ instead

Status: ✅ Confirmed working by user

Solution 2: Change Default Config Directory (Recommended Fix)

Recommended permanent fix for WinBoat:

• Change the default configuration directory from ~/.winboat/ to ~/winboat/ (non-hidden)
• Or use ~/.config/winboat/ which Snap may have access to
• Update installation script to create non-hidden directory
• Document Snap compatibility requirements

Solution 3: Grant Snap Home Access (Workaround : may be)

Connect the Docker snap to home interface:

sudo snap connect docker:home

Quality Notice

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

[nicolodon]

An additional workaround that worked for me is following the docker installation guide from .deb instead of using snap.

[lrkwz]

A command line or environment variable to configure the default config dir would be fantastic.