Bottles

This is a community package of Bottles, maintained independently and unaffiliated with the Bottles project. It is built from the project's own Flatpak manifest, changed only to target the GNOME 50 runtime, and follows upstream releases automatically.

Bottles runs Windows applications and games on Linux. Each program lives in its own bottle — a Wine prefix with its own runner, libraries and settings — so one application's configuration never disturbs another's, and a broken bottle can be thrown away without touching the rest.

• Environments that preset a bottle for gaming, for ordinary applications, or from scratch.
• Per-bottle runners: Wine, Proton and Bottles' own builds, installed and switched independently.
• DXVK, VKD3D, DXVK-NVAPI and LatencyFleX managed per bottle, with a built-in installer catalogue for common software.
• Versioning: snapshot a bottle before a risky change and roll back to it.
• Sandboxed dependency and registry management, task and terminal views, and per-bottle performance tuning.

Everything the package needs is bundled: Wine, the 32-bit compatibility stack, the Vulkan and GStreamer pieces, and Bottles' own tooling. Nothing is required on the host.

Sandbox: display, GPU, audio, network, and full device access so gamepads and racing wheels reach the software you run. Bottles and their prefixes live in the app's own data directory, which persists across restarts without any host directory being opened. The one filesystem grant is for umu's runtime, under ~/.local/share/umu and ~/Games/umu.

That means the app can see no other host directories out of the box. To install from a directory of your own, or to keep a games library outside the sandbox, grant it explicitly:

flatpak override --user --filesystem=~/Games com.usebottles.bottles

Replace the path with your own, repeat the flag for more directories, and undo everything with:

flatpak override --user --reset com.usebottles.bottles