How To Install Bottles on Fedora 45

Install Bottles on Fedora 45

Fedora 45 came out on November 3, 2026, and it ships with GNOME 51. Plenty of people are already asking the same practical question on fresh installs. How do you run that one Windows program you can’t replace, whether it’s an accounting tool, an old CAD viewer, a launcher or a game, without dual booting or standing up a VM?

Bottles is a good answer. It wraps Wine and Proton in a GUI that manages isolated environments, which it calls “bottles”. It also handles runners, DXVK and dependencies. The catch is that how you install it matters more than most guides admit. Fedora’s repositories carry an RPM, the project recommends Flatpak, and the two don’t behave the same way. A user on r/linux_gaming reported that the Fedora RPM left the Runners and DLL Components tab empty (upstream issue #4229), while the Flatpak worked properly. That is the kind of detail that costs an evening if you find it by accident.

This guide covers the install path that holds up in practice. It also covers why Flatpak is the better choice, how to give Bottles access to the files and drives it needs, and how to tune it. The troubleshooting section covers the failures that come up most often, including NVIDIA driver mismatches, missing desktop entries and permission errors. The commands are written for Fedora 45, and the Flatpak parts apply on Ubuntu, Debian and AlmaLinux with only the package-manager lines changed.

What Bottles Actually Does

Bottles is a Wine manager. Wine translates Windows API calls into POSIX calls so Windows binaries can run on Linux. Bottles adds structure on top. Each bottle is a separate Wine prefix with its own registry, its own C: drive and its own runner and dependency set.

That isolation is the main point. Install a .NET 4.8 app and a DirectX 9 game into one shared prefix, and sooner or later one will break the other. Separate bottles stop that.

Bottles offers three environments when you create a bottle: Application, Gaming and Custom. Gaming pre-enables DXVK and related options. Application keeps things plain. Custom lets you pick Wine or Proton runners yourself. The runner docs describe two runner types, Wine and Proton. Wine is used for all environments and for imported external prefixes. Proton can be installed from Preferences and chosen when you create a Custom bottle. You can also switch a bottle from Wine to Proton later in its settings.

Why Flatpak Is the Right Choice on Fedora 45

Fedora can install Bottles with sudo dnf install bottles, and some tutorials still suggest it. That works on paper. In practice, Flatpak is the better path, for three reasons.

First, the project itself says so. The Bottles site calls Flathub “the official and recommended way to install Bottles” and says it is supported on all major distributions. The Arch Wiki notes that the developers strongly recommend Flatpak because it provides sandboxing.

Second, the RPM has had bugs the Flatpak doesn’t. The Runners and DLL Components issue mentioned above is one.

Third, sandboxing matters. Bottles runs arbitrary Windows executables. Wine is not a security boundary, and a Windows binary run under Wine can read anything your user account can read. Flatpak gives you a fence around that. It isn’t perfect, but it is far better than nothing.

There is a trade-off. Inside the sandbox, Bottles can’t see your whole home directory or other drives until you grant access. That is manageable, and the permissions section below covers it.

Before You Start

Check the basics first. Fedora’s own download page lists 4 GB of RAM and 40 GB of disk as the general recommendation. Bottles adds more on top. Each bottle with a runner, DXVK, VKD3D and a few redistributables easily takes 3 to 6 GB, and games take far more. If you plan to keep several bottles, budget disk space accordingly.

Update the system first:

sudo dnf upgrade --refresh

Reboot if the kernel or graphics stack was updated. This matters more than it looks. A pending kernel update with an NVIDIA driver is a common source of confusing Vulkan errors later.

Next, confirm your GPU stack. For Vulkan on Mesa (AMD and Intel):

sudo dnf install vulkan-tools mesa-vulkan-drivers
vulkaninfo --summary

If vulkaninfo lists a device, you’re in good shape. DXVK depends on Vulkan, so a broken Vulkan stack on the host means broken Windows games in Bottles.

Step-by-Step: Install Bottles via Flatpak

Step 1: Confirm Flatpak and Flathub

Fedora Workstation includes Flatpak. Fedora’s own filtered Flatpak remote exists, and Atomic images now ship filtered Fedora Flatpak runtimes alongside verified Flathub support. To get the full Bottles build, you want Flathub itself. Check what you have:

flatpak --version
flatpak remotes

If Flathub isn’t listed, add it. Use the user scope to keep things clean:

flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

If Flathub is already enabled system-wide, that’s fine too. Just be consistent. Mixing system and user installs of the same app is a classic source of strange behavior. The user report cited earlier specifically advised installing Bottles in user scope to avoid odd launch behavior.

Step 2: Install Bottles

flatpak install --user flathub com.usebottles.bottles

Flatpak will pull the app plus the GNOME runtime and the Freedesktop GL extensions. Expect a download of a few hundred megabytes on a fresh system. Confirm with y when asked.

Step 3: Launch It

flatpak run com.usebottles.bottles

Or open it from the GNOME Activities overview. The first launch runs a short onboarding process that downloads the default components: a Wine runner (Soda or Caffe, depending on the version), DXVK and VKD3D. Let it finish. Interrupting it is how people end up with a half-initialized components list.

Step 4: Check Where Data Lives

For the Flatpak, bottle data lives under:

~/.var/app/com.usebottles.bottles/data/bottles/

Knowing this path helps when you back up, clean up or debug. A quick size check:

du -sh ~/.var/app/com.usebottles.bottles/data/bottles/*

Creating Your First Bottle

Click the plus button and give the bottle a name that tells you what it’s for, such as office-legacy or games-battlenet. Naming discipline pays off when you have eight of them.

Pick the environment. For a business application, choose Application. For anything using Direct3D heavily, choose Gaming. Bottles will build the prefix, which takes a minute or two.

Then run an executable. Inside the bottle, use “Run Executable” and point to the .exe or .msi. If you installed the program elsewhere, add it manually to the Programs list so you can launch it with one click.

One practical note on installers. Bottles has an Installers section with automated recipes. These use the same dependency manager available manually in the bottle, so each step is handled like a manual dependency install. Under Flatpak, installers do not currently create application-menu launchers by themselves. That leads to the next section.

Permissions: Giving Bottles the Access It Needs

Flatpak’s sandbox is why Bottles works safely, and also why it sometimes looks broken. A program inside a bottle can’t see ~/Documents or a second drive unless you allow it.

Use Flatseal if you prefer a GUI:

flatpak install --user flathub com.github.tchx84.Flatseal

Or use the command line. To let Bottles see a particular folder:

flatpak override --user --filesystem="$HOME/Documents" com.usebottles.bottles

Linux Magazine’s walkthrough uses the same pattern with a shorter path form, for example granting access to the pictures directory. Grant only what’s needed. Avoid --filesystem=home unless you have a reason. It removes much of the point of sandboxing.

Storing bottles on another drive

Large games can exceed 100 GB. If your home partition is small, put bottles on a bigger disk and grant access to it:

flatpak override --user --filesystem=/mnt/games com.usebottles.bottles

Then set the custom bottles path in Bottles’ preferences. Make sure the drive is mounted with proper ownership. An NTFS partition mounted without correct options causes permission and case-sensitivity trouble. If you can, use ext4 or XFS for the games disk. Btrfs is Fedora’s default on Workstation, and it works fine, but consider disabling copy-on-write on directories that hold large, constantly rewritten files:

chattr +C /mnt/games/bottles

Set this on an empty directory, since it only affects newly created files.

Desktop entries

Because the Flatpak is sandboxed, it can’t write launchers into your applications folder by default. Close Bottles and run:

flatpak override com.usebottles.bottles --user --filesystem=xdg-data/applications

Then, in a bottle’s Programs list, use the kebab menu next to a program and select Add Desktop Entry. The program will then appear in GNOME’s app grid like any native app.

Runners, DXVK and Components

A runner is the Wine build executing your program. Different runners carry different fixes. A program that crashes on one often runs fine on another. Bottles lets you change runners per bottle. You can download extra ones from the global Preferences, and they then become available to every bottle.

DXVK translates Direct3D 9, 10 and 11 to Vulkan. Enabling it in a bottle’s Components section can noticeably improve graphics performance in games and visually intensive tools. VKD3D-Proton does the same for Direct3D 12.

A sensible approach:

  • Start with the default runner and leave settings alone.
  • Test the program. If it works, stop tuning.
  • If it fails, change one thing at a time: runner, then DXVK version, then dependencies.
  • Keep notes. Six months later you won’t remember which combination worked.

When an application complains about missing libraries, check the Dependencies page in the bottle. Search for the missing component, such as vcredist, .NET or core fonts, and install it. Many “random crashes” are just a missing Visual C++ runtime.

NVIDIA Users: Read This Section

NVIDIA on Fedora needs more care than AMD or Intel. Fedora doesn’t ship the proprietary driver by default. Most people install it from RPM Fusion, and the Flatpak needs a matching GL extension.

The key rule: the host driver version and the Flatpak NVIDIA extension version must match exactly. A mismatch leads to zero Vulkan devices and silent crashes, with applications such as Battle.net failing without a useful error.

Check both:

nvidia-smi | head -n 5
flatpak list --runtime | grep -i nvidia

If they differ, update Flatpaks and reboot:

flatpak update
sudo reboot

After any kernel or driver update, reboot before launching Bottles. Without it, nvidia-smi can report a driver/library version mismatch, which leaves the Flatpak extension out of sync. It looks like a Bottles bug. It isn’t.

Hybrid laptops add one more layer. Use PRIME offload so the game runs on the discrete GPU. For a Flatpak, you can set environment variables per bottle in Bottles’ settings, or globally via override:

flatpak override --user --env=__NV_PRIME_RENDER_OFFLOAD=1 --env=__GLX_VENDOR_LIBRARY_NAME=nvidia com.usebottles.bottles

Test with a small program before blaming the game.

Troubleshooting Common Errors

Runners or components list is empty

This is typical of the RPM build. Remove it and use the Flatpak:

sudo dnf remove bottles
flatpak install --user flathub com.usebottles.bottles

Your existing bottle data from the RPM lives in a different path, so migrate it manually if needed.

Bottles won’t start

Run it from a terminal to see the error:

flatpak run com.usebottles.bottles

If you installed it both system-wide and per-user, remove one:

flatpak list --app | grep -i bottles
flatpak uninstall --system com.usebottles.bottles

Application crashes without an error

Check, in order: Vulkan on the host (vulkaninfo --summary), NVIDIA driver and extension parity, then runner choice, then dependencies. Switching runners is the cheapest test.

No Vulkan devices found

On NVIDIA, this is almost always a version mismatch. On AMD or Intel, install mesa-vulkan-drivers and reboot.

Files or drives aren’t visible

You need a Flatpak override. Add the path with flatpak override --user --filesystem=/path, restart Bottles, and retry.

No desktop entry appears

Apply the xdg-data/applications override, then add the entry from the Programs menu.

Fonts look wrong or text is missing

Install fonts from the Dependencies page. For font-heavy launchers, installing all fonts via winetricks-based dependencies is often what fixes blank text.

Debugging with logs

Enable debug logging in Bottles, or launch with Wine debug variables set in the bottle’s environment settings. Keep logs short. WINEDEBUG=err+all is usually enough, since verbose channels generate gigabytes quickly.

r00t is an experienced Linux enthusiast and technical writer with a passion for open-source software. With years of hands-on experience in various Linux distributions, r00t has developed a deep understanding of the Linux ecosystem and its powerful tools. He holds certifications in SCE and has contributed to several open-source projects. r00t is dedicated to sharing her knowledge and expertise through well-researched and informative articles, helping others navigate the world of Linux with confidence.

Related Posts