You typed dnf install minecraft and got nothing
You installed Fedora Workstation, opened the terminal, and typed sudo dnf install minecraft. The package manager returned Error: Unable to find a match: minecraft. You checked GNOME Software and found no results. You remember the Windows installer was a single executable, but Fedora refuses to provide a package. You need to play the game, and you need to understand why the system is blocking you and how to install the launcher without compromising your system integrity.
Why Fedora does not ship Minecraft
Fedora maintains a strict policy regarding its official repositories. The repos contain only free and open-source software. Minecraft is proprietary software owned by Microsoft. The Fedora project does not distribute proprietary binaries. This policy ensures the distribution remains legally clean and avoids licensing conflicts. It also means dnf will never install Minecraft.
The solution is Flatpak. Flatpak is a sandboxed application format that runs across all Linux distributions. Flathub is the central repository for Flatpak apps. It hosts proprietary software that Fedora cannot include. When you install Minecraft via Flatpak, you are not adding a package to the Fedora system. You are downloading a self-contained application bundle that shares the kernel but isolates its files and libraries. This isolation prevents dependency conflicts and keeps your system stable.
Fedora's release cadence is six months. The N-2 release goes end-of-life when N+1 ships. Flatpak apps update independently of the Fedora release cycle. You can keep the game updated even after a major system upgrade. Trust the package manager for system components. Use Flatpak for applications that live outside the Fedora repo policy.
Install the official launcher via Flatpak
The official Microsoft launcher is available on Flathub. This is the recommended method for a vanilla experience. It requires a Mojang or Microsoft account to log in.
Here's how to add the Flathub repository so Flatpak can find the Minecraft launcher.
flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
# --if-not-exists prevents an error if you already added Flathub in the past
Install the launcher and start it. The launcher handles downloading the game client files on first run.
flatpak install flathub com.mojang.Minecraft
# Install the official launcher from Flathub
flatpak run com.mojang.Minecraft
# Launch the application immediately after installation
The Flatpak sandbox restricts file access by default. The launcher can read its own data directory, but it cannot write to your home folder or access screenshots. If the launcher cannot save screenshots or load mods from ~/Downloads, you need to expand the sandbox permissions.
Grant the launcher read-write access to your home directory if you need file access.
flatpak override --user --filesystem=home com.mojang.Minecraft
# Grant the launcher read-write access to your entire home directory
# This allows saving screenshots and loading mods from ~/Downloads
Grant filesystem access only if you need it. The sandbox protects your system for a reason.
Use PrismLauncher for mods and multiple instances
PrismLauncher is the standard for modded Minecraft on Linux. It is an open-source fork of MultiMC. It supports multiple game instances, mod loaders like Fabric and Forge, and automatic Java version management. Each instance runs in isolation. You can have a vanilla instance and a heavily modded instance side by side without conflicts.
Install PrismLauncher from Flathub and start the configuration wizard.
flatpak install flathub org.prismlauncher.PrismLauncher
# Install PrismLauncher from Flathub
flatpak run org.prismlauncher.PrismLauncher
# Start the launcher to configure instances
PrismLauncher guides you through Microsoft account login and Java selection. It downloads the correct Java version for each instance automatically. You do not need to manage system Java packages for modded gameplay.
Use PrismLauncher when you plan to mod the game. The official launcher struggles with mod management.
Verify graphics drivers and Java runtime
Minecraft relies on OpenGL. Low performance or crashes often stem from missing drivers rather than the game itself. Verify your driver status before adjusting game settings.
Install diagnostic tools and check the OpenGL version string.
sudo dnf install mesa-demos
# Install diagnostic tools for graphics drivers
glxinfo | grep "OpenGL version"
# Display the OpenGL version string to verify hardware acceleration
If glxinfo reports a software renderer like llvmpipe, your GPU driver is not active. AMD and Intel GPUs use Mesa, which is included by default. NVIDIA GPUs require proprietary drivers.
Install the NVIDIA driver via RPM Fusion if you have an NVIDIA GPU. The akmod package compiles the driver against your current kernel.
sudo dnf install akmod-nvidia
# Install the NVIDIA driver kernel module builder
# akmod compiles the driver against your current kernel automatically
Reboot after installing akmod-nvidia. The kernel module must compile and load before the game will use the GPU.
Both launchers bundle their own Java runtimes. You do not need system Java for the game. Install OpenJDK only if you are running standalone .jar files or testing mods from the command line.
sudo dnf install java-21-openjdk-devel
# Install OpenJDK 21 for development and command-line testing
java -version
# Confirm the runtime is active and matches the expected version
dnf upgrade --refresh is the normal weekly maintenance command for system packages. flatpak update handles application updates. They are separate commands. Run flatpak update to keep the launcher current.
Common errors and how to fix them
The launcher crashes on start. Check the logs before reinstalling. Flatpak apps log to the journal.
journalctl -xeu flatpak
# Show recent logs for Flatpak with explanatory text
# -x adds explanations, -e jumps to the end of the log
If you downloaded files manually and the launcher refuses to read them, SELinux labels might be wrong. SELinux enforces mandatory access controls. Files created outside the sandbox may have incorrect context.
Restore correct SELinux context labels recursively for the launcher data directory.
restorecon -Rv ~/.local/share/PrismLauncher/
# Restore correct SELinux context labels recursively
# -v prints every file that gets fixed
Check recent AVC denials for more detail if the issue persists. SELinux denials show up in the journal with a one-line summary. Read those before disabling SELinux.
ausearch -m avc -ts recent
# Search audit logs for recent access vector cache denials
If you host a local server and friends cannot connect, the firewall might be blocking the port. Local play needs no firewall changes. Open the default port if you are hosting.
sudo firewall-cmd --permanent --add-port=25565/tcp
# Add the default Minecraft server port to the persistent firewall rules
sudo firewall-cmd --reload
# Apply the new rules to the running firewall immediately
Run firewall-cmd --reload after every rule change. The runtime config and persistent config diverge otherwise.
Audio is silent in the game. Flatpak apps share the host audio server. Fedora uses PipeWire by default. If PipeWire is running, Flatpak works. If you have a custom PulseAudio configuration, it might break sandboxed audio. Verify the audio server is active.
pactl info | grep "Server Name"
# Check which audio server is active
If the output shows PipeWire, the server is correct. Restart the launcher. If audio is still missing, check the Flatpak permissions.
flatpak info --show-permissions com.mojang.Minecraft | grep -A 5 context
# Display sandbox permissions for the Minecraft launcher
# Verify that audio access is not explicitly denied
Run journalctl -xe first. Read the actual error before guessing.
Choose the right launcher
Use the official Flatpak launcher when you want a stable, vanilla experience with zero configuration. Use PrismLauncher when you are installing mods, managing multiple game instances, or switching between Fabric and Forge. Use Bottles when you encounter a Windows-only modding tool that refuses to run on Linux. Use the system package manager for drivers and Java, but keep the game itself in Flatpak to avoid dependency conflicts.