Flatpak Repositories and Applications
RHEL 10 removed the whole container domain from EX200 and added two Flatpak objectives in its place, so there is very little RHCSA material on this yet. Configuring access to a repository and installing from it are both done here on a real remote, and both of the errors a first attempt produces are captured.
Managing Software Guide 15 of 67 Intermediate
- OSRHEL 10.0
- Kernel6.12.0-55.9.1.el10_0
- dnf4.20.0
- Flatpak1.16.0
- TimeAbout 16 min
The rhel remote is pre-configured on every RHEL 10 install and points at oci+https://flatpaks.redhat.io/rhel/, which needs subscription entitlement - it cannot even be listed without it. This guide adds Flathub instead. The commands are identical whichever remote you use, which is what the objective is about.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| RHCSA-A01 | 192.168.0.31 | RHEL 10.0 | Practice node (graded) - spare /dev/sda | 2 Core | 4 GB | 50 GB + 15 GB |
This guide includes
Use this because RHEL 10 removed the container domain and added two Flatpak objectives in its place. This matters because the remote the system ships with does not work here - so configuring one is the first objective rather than a preliminary.
- checking what is already configured
- finding why the shipped remote will not work
- configuring access to a repository, which is the first of the two objectives
- finding an application and installing it, including why that needs root
- reading what you actually installed, then removing it and reclaiming the runtimes
Before you start
- Outbound internet, and roughly 2 GB free on
/var. - The session adds and removes a remote, and installs and removes an application.
-
What is already configured
-
Why the shipped remote will not work here
-
Configuring access to a repository
-
Finding an application
-
Installing, and why it needs root
-
What you actually installed
-
Removing, and reclaiming the runtimes