Latest

Finance

Why everyone uses Flatpak on Linux nowadays

Discover how Flatpak solved Linux installation problems and why it has become the standard for the desktop

Flatpak and the transformation of Linux application distribution:
Flatpak and the transformation of Linux application distribution:

The fragmentation of desktop platforms across Linux-based operating systems has historically been one of the biggest obstacles to mass adoption of this ecosystem by software developers and end users. Traditionally, application distribution required creating multiple packages specific to each distribution, such as .deb files for Debian or Ubuntu, and .rpm for Fedora or Red Hat Enterprise Linux (RHEL).

This fragmented packaging model forces developers to deal with what is known as "dependency hell", where updating a shared system library could break the compatibility of multiple installed applications.

To solve this problem structurally, the need arose to design a universal, independent packaging format that would allow applications to be isolated from the base system, guaranteeing cross-distribution compatibility and improving overall system security. The result of this effort is Flatpak, a technology solution that redefines how desktop applications are distributed, run and secured in the Linux ecosystem.

Flatpak: Origins, evolution and historical milestones

The origin of Flatpak technology is closely tied to the professional career of Alexander Larsson, a developer with extensive experience in the design of Linux desktop environments and container systems at Red Hat.

Although Red Hat (owned by IBM) funded a substantial part of Larsson's work by allowing him to dedicate time from his working day to the project, Flatpak has remained under the governance of a fully independent open source community, free of exclusive corporate dependencies (vendor lock-in).

Larsson's original motivation was to apply the lessons learned from developing server containers to the desktop application space, radically simplifying software distribution.

The leadership transition and current development

Despite the undeniable commercial success and the platform's widespread adoption by users, the project's development has seen significant changes in its pace and leadership. Toward the end of the recent development period, a slowdown has been observed in the incorporation of major architectural changes into Flatpak's main code.

This situation is mainly due to the fact that historical figures of the project, including Alexander Larsson himself, have stepped away from day-to-day development of the codebase, leaving maintenance and security fixes in the hands of a small group of volunteer contributors. This handover has created a bottleneck in the review of merge requests, stretching over months the time needed to incorporate new features proposed by the community.

Microsoft finally has native, real Linux containers on Windows

Even with these limitations in core development, the ecosystem continues to expand, driven by specific corporate and industrial needs. On one hand, Red Hat has pushed for the integration of Flatpaks into the base installation of enterprise systems through the development of a component called flatpak-preinstall, slated for official inclusion in Red Hat Enterprise Linux (RHEL) 10.

This development, started by Owen Taylor and Kalev Lember, aims to allow system administrators and manufacturers to preconfigure essential desktop applications from the very first deployment of the operating system, guaranteeing a consistent user experience in corporate environments.

Technical architecture and isolation mechanisms

Flatpak's robustness rests on a meticulously designed technical architecture that combines established Linux kernel technologies with new desktop interoperability standards.

Unlike server containers that isolate entire network infrastructures, Flatpak's architecture is geared toward maintaining graphical consistency, peripheral access and storage optimization on multi-user systems.

OSTree and content-addressable storage

File storage and distribution in Flatpak are managed through OSTree, a technology directly influenced by the Git version control model.

While Git tracks source code files, OSTree is optimized to efficiently manage complete trees of binary files and system images. The internal operation of an OSTree repository on the user's disk is organized under a very precise directory structure:

  • config file: Stores the local configuration of the repository path and file system parameters.
  • refs directory: Contains references to the installed software branches, structured hierarchically (for example, under refs/heads/master). Each reference file contains a cryptographic signature in SHA-256 format (commit ID) that unambiguously points to the current state of that software branch.
  • objects directory: Central storage of structured data, classified into subdirectories named after the first two hexadecimal characters of their SHA-256 checksum to avoid saturating flat folders.

Because OSTree indexes objects based solely on the content of their SHA-256 signature, if multiple applications or runtimes contain the same binary file, it is physically stored only once on the hard drive. When performing an installation, Flatpak creates hard links from the local OSTree repository to the runtime file system.

This design minimizes disk storage consumption, reduces RAM usage and notably optimizes bandwidth consumption during the update process.

Process isolation via Bubblewrap

In addition to all this, and to prevent applications from interfering with the host operating system or extracting private information from other processes, Flatpak confines their execution in a controlled environment (sandbox) through the low-level utility Bubblewrap.

Originally developed within Red Hat's Project Atomic, Bubblewrap is a security tool that allows users without administrative privileges to launch secure containers through direct calls to the Linux kernel. To achieve this level of isolation, the utility uses three key kernel mechanisms:

  • Namespaces: They segment the network, process, user and mount resources visible to the application. This way, the executed program believes it is on an operating system exclusive to itself.
  • Bind mounts: They strictly redefine the visible directory map, creating virtual temporary folders and restricting real access to the machine's physical root folders.
  • Seccomp (secure computing filters): They strictly restrict and filter the system calls (syscalls) the application can make to the processor kernel, neutralizing at the root any attempt to exploit system flaws or escalate privileges. Although at this point it should be noted that seccomp is not "as secure as it is made out to be." The reality is that seccomp's highly complex structure has made it a target of attacks throughout its history; on HackTricks they discuss this and will give you an idea of the level of security you can achieve with this technology.

The Linux era: Why developers and node operators choose the penguin in 2026

Flatpak implementation and automation guide

Setting up a Flatpak-based environment on traditional Linux operating systems requires configuring the runtime engine, linking the central Flathub store and implementing system triggers to keep desktop applications updated autonomously.

Environment setup on Debian and Ubuntu distributions

To enable Flatpak support on Debian- or Ubuntu-based distributions that do not include it by default, the package must be installed through the APT package manager from the administration console, using these commands:

sudo apt update sudo apt install flatpak

To integrate the visual installation gateway on GNOME desktops, it is recommended to install the system software environment together with the specific package communication plugin:

sudo apt install gnome-software-plugin-flatpak gnome-software

Initialization and modification of remote repositories

Once the engine is configured, the central Flathub repository is linked at the global file system level:

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

On Flathub you can find the additional instructions to install and enable the repository on other distributions.

Common software management operations via terminal

For agile interaction and daily management of the Flatpak application catalog, the flatpak command-line tool has a structured set of maintenance instructions:

Searching for applications in the catalog:

flatpak search libreoffice

Installing packages from the stable branch in the system profile:

flatpak install flathub org.libreoffice.LibreOffice

In any case, Flathub has a web search engine that will let you browse the more than 4000 applications currently available there.

Conclusions

The consolidation of the Flatpak ecosystem represents a fundamental milestone in the evolution of Linux-based desktop platforms. Through an engineering design based on software decentralization, file immutability, massive deduplication by cryptographic hash and robust runtime isolation, this technology has effectively alleviated historical problems of compatibility and fragmentation in desktop application distribution.

AI threatens cybersecurity: Chaos in Linux and software repositories

Although the project faces challenges associated with the slowdown in development of its core codebase due to generational leadership handovers. In addition, constant corporate expansion in enterprise operating systems and the outstanding maturity of its unified Flathub store ensure that the format will continue to operate as one of the indispensable cornerstones of the future of usability and security on desktop Linux.

José Maldonado

Author

José Maldonado

Activist and blogger on technology, free software and blockchain.

The latest
From Huang to Botín, from Zara to Byron: corporate responsibility in global capitalism

Keep reading