The Ultimate Guide to Running a Windows 11 Environment on Ubuntu with Winboat

March 09, 2026 2022 technical

Running Windows applications natively on Linux has always been a challenge, but Winboat makes it remarkably seamless by leveraging Docker and QEMU. On a modern machine like a 13th Gen i7 with 16GB of RAM, you can run a full Windows 11 instance without breaking a sweat.

In this guide, I’ll walk you through the complete installation process, from setting up Docker to fixing pesky startup sandbox errors.

1. Prerequisites: System Setup

Winboat is built on top of Docker and requires a high-performance RDP client for the best experience.

Step A: Install Docker and FreeRDP

Open your terminal and run:

# Update your package list
sudo apt update

# Install Docker
sudo apt install -y docker.io

# Install FreeRDP 3 (Critical for the Winboat display)
sudo apt install -y freerdp3-x11

Step B: Grant Docker Permissions

To run Winboat without needing sudo every time, you must add your user to the docker group:

sudo usermod -aG docker $USER

[!IMPORTANT] You must log out and log back in (or restart your computer) for this group change to take effect. If you don’t, Winboat won’t be able to find the Docker daemon.

2. Installing Winboat

Winboat is distributed as an AppImage, which is a self-contained executable that doesn’t mess with your system libraries.

Download the latest release:

wget https://github.com/TibixDev/winboat/releases/download/v0.9.0/winboat-0.9.0-x86_64.AppImage

Make it executable:
```
chmod +x winboat-0.9.0-x86_64.AppImage
```

Recommended Performance Settings

When you first run the setup wizard, I recommend these values for a balance between speed and system stability:

RAM: 8GB (8192 MB)
CPU Cores: 4 to 6
Storage: 64GB (NVMe recommended)

3. Troubleshooting Common Issues

Issue 1: SUID Sandbox Error (Ubuntu 24.04)

On modern Linux distributions, you might see a fatal error about the chrome-sandbox not being configured correctly. This is a security feature that sometimes conflicts with AppImages.

The Fix: Launch Winboat with the --no-sandbox flag:

~/winboat-0.9.0-x86_64.AppImage --no-sandbox

Issue 2: Command Not Found

If you want to simply type winboat in your terminal instead of the full AppImage path, you can set up a permanent alias.

Open your .bashrc: nano ~/.bashrc

Add this line at the bottom:

alias winboat="~/winboat-0.9.0-x86_64.AppImage --no-sandbox"

Save and apply: source ~/.bashrc

Issue 3: Missing Launcher?

If you ever “lose” your Winboat command or the AppImage disappears, check your ~/ (Home) directory or your Trash. If it’s in the Trash, move it back to Home and ensure it still has its execution permissions (chmod +x).

Issue 4: Small Fonts and UI (High-DPI Scaling)

If you have a high-resolution display, Winboat and its Windows environment might appear very small. You can fix this by adjusting the scaling factor in the configuration file.

Open the config file: nano ~/.winboat/winboat.config.json
Change the "scale" and "scaleDesktop" values from 100 to 200, 300, or even 400 (representing 200%, 300%, or 400% scaling).
Restart Winboat for the changes to take effect.

Issue 5: High RAM Usage / Reclaiming Resources

Winboat runs a full Windows environment, which typically consumes around 8GB of RAM. If you notice your system slowing down, you can safely stop the background process to reclaim your memory without losing any of your work or configuration.

To stop Winboat and free your RAM: Open your terminal and run:

sudo docker stop WinBoat

When you want to use it again, simply type winboat (or run your alias). It will start back up exactly where you left off!

Bonus: On-Demand Startup (Zero RAM on Boot)

If you want to ensure Winboat uses zero RAM unless you actually launch it, you can configure Docker to only start when you need it.

Disable Docker at Boot:
```
sudo systemctl disable docker
```

Add a Smart Startup Function: Replace your winboat alias in ~/.bashrc with this function:

winboat() {
    if ! systemctl is-active --quiet docker; then
        echo "Starting Docker service..."
        sudo systemctl start docker
    fi
    ~/winboat-0.9.0-x86_64.AppImage --no-sandbox "$@"
}

Now, typing winboat will automatically start the engine and then the app, keeping your system fast the rest of the time!

4. Why Winboat?

Unlike traditional virtual machines, Winboat feels “native.” Once you install Windows apps (like Microsoft Office), you can right-click them inside Winboat and select “Add to Desktop.” This creates a shortcut in your Linux environment that launches the Windows app directly!

Happy computing! 🚀💻