Flatpak - RHEL 10 Package Manager

[Trevor]

Just when I'm starting to get my feet underneath me with dnf,
here comes another package manager.

Is this new package manager, Flatpak, in someway based on, 
influenced by, or connected with, AI?

[Meher_Askri]

Not exactly, the idea behind flatpak is to make apps distro agnostic, which means the same app can run on Debian, Fedora, Arch...., without caring about DEB vs RPM.

So Instead of using DEB or RPM, Flatpak ship the app with its runtime and run it in a sandbox. However there still some limitation because Flatpak is not meant for system software such as kernel modules, system services, network daemons, anything that needs deep integration with the OS.

[Travis]

@Trevor -

Flatpaks aren't new and don't have anything to do with AI in the sense you are thinking. Flatpaks are meant to be "portable" applications that are generally user-space applications meaning users can install a Flatpak for use on a system (even without having SUDO access). In general, most Flatpak applications are geared towards end-users and many of these applciations are GUI-based. Flatpaks are typically designed for "desktop-style" Linux systems for end-users and not for Enterprise Servers. They typical RPM package manager installs applications and components at the system-level and requires that users have elevated permissions to be able to install these packages. Flatpaks on the other hand do not require this level of permissions.

Flatpaks are very similar to containers in that they run in a "sandboxed" environment and download the various layers and runtimes needed for the application. Another portable application that is available is called a SNAP.

https://flatpak.org/

https://snapcraft.io/

Both of these technologies are supposed to make apps more portable and accessible towards end-users.

[Trevor]

I'm just going to have to sit down, and spend some tiime 
digesting this Flatpak thingy.  Your explanation indicates
that my thinking was out in left field.  Ouch!

Thanks Travis!

[Chetan_Tiwary_]

@Trevor It has nothing to do with AI and is there since 2015 I guess.

With the arrival of RHEL 10, the inclusion of Flatpak highlights Red Hat’s strategy to make desktop applications easier to manage without risking the stability of the system’s core packages. This approach allows users to install the latest software without needing deep, potentially destabilizing integrations. Ultimately, this is an evolution of classical software distribution as it provides a more flexible, stable way to manage applications across various environments, focusing on architectural reliability rather than being an automated or AI-driven tool.

[Trevor]

My goodness - around since 2015?  And I'm just getting wind
of it at the closeout of 2025?  Looks like I'm going to have to
devote more time to my RHEL reading, and less time on the 
comic books

Thanks Chetan!!!

[Priyanshu20041]

@Trevor 

Flatpak isn’t AI-based or AI-driven—it’s simply another way to deliver applications on Linux.

While dnf manages core system packages (kernel, libraries, services), Flatpak focuses on desktop applications, running them in isolated sandboxes with their own dependencies. This improves security, avoids dependency conflicts, and makes apps more portable across different Linux versions.

In RHEL 10, Flatpak complements dnf rather than replacing it. The OS stays RPM-managed, while Flatpak provides a safer and more flexible way to install user-facing applications.

[Trevor]

Thanks Priyanshu20041 for your response.

Your comment, "Flatpak focuses on desktop applications, running
then in isolated sandboxes..." prompts a couple of questions.
First, is Flatpak going to actually run the applications, or is it going
to install them?
Second, does Flatpack ONLY run/install the desktop applications in
the isolated sandboxes?
Last (for now), if there is a desktop application that I can use Flatpak
for, do I have the option to use dnf to install that same application?

[Priyanshu20041]

Thanks , Exactly — Flatpak installs the application along with its dependencies, and when you launch it, it runs inside its sandbox. The sandboxing is primarily for desktop applications, so other system apps aren’t affected.

And yes, if the same app is available via dnf , you can install it that way too — but it won’t be sandboxed. Flatpak gives you the choice between isolation and portability versus standard system-wide installation.

[Travis]

@Trevor -

Flatpak applications are basically containerized applications from a "comparison" standpoint. By saying desktop applications, it is traditionally a user application and can be installed as a user. It is also possible to install Flatpaks "system-wide" as the root user. So an example of a Flatpak application would be Firefox and Gimp. Both of these are traditionally installed as RPMs on Linux, but also available as Flatpaks.

https://flatpak.org/

Also, on my Linux system, I'm using the Slack application as a Flatpak. You should have access to the newer RHEL10 RHCSA content as RHCA instructor. This has information about Flatpaks and we have a local Flatpak repository in this course on the "Utility" server.

Flatpak does run the applications because they are "layered" in a sense similar to containers as some Flatpaks require extra runtimes to be used, so when you install some Flatpaks, you will see it pull in different components that are required for the Flatpak. These "runtimes" get installed once and can be reused for multiple applications.

A quick read for information can be here: https://docs.flatpak.org/en/latest/getting-started.html

I suggest looking at some of the RHCSA content around Flatpaks in your safe lab environment where you can play all you want there. This way you can play around with them and if something breaks, you can reset the environment.