Chapter 21. Installing Flatpak applications on hosts
After you synchronize Flatpak repositories in Satellite, you can install Flatpak applications on hosts from Satellite Server or Capsule Server. On each host, add a Flatpak remote, authenticate to the container registry, and install the applications you need.
Additional resources
21.1. Configuring Podman to trust the certificate authority Copy linkLink copied to clipboard!
Configure Podman to trust the Satellite certificate authority so that you can push and pull container images without disabling TLS verification.
Podman locates the CA file in the /etc/containers/certs.d/ path. Copy the root CA file to that path, with the exact path determined by the server hostname, and name the file ca.crt.
In the following examples, replace hostname.example.com with satellite.example.com or capsule.example.com, depending on your use case.
Prerequisites
- You have the root CA certificate file for Satellite Server or Capsule Server.
- You have root or sudo access on the host where Podman is installed.
Procedure
Create the relevant directory:
# mkdir --parents /etc/containers/certs.d/hostname.example.comCopy the CA file to the directory:
# cp My_Root_CA.pem /etc/containers/certs.d/hostname.example.com/ca.crt
Verification
Verify that you no longer need to use the
--tls-verify=falseoption when logging in to the registry:$ podman login hostname.example.com
21.2. Installing Flatpak applications on a host from Satellite Server Copy linkLink copied to clipboard!
Connect your host to the Flatpak remote on Satellite Server, authenticate to the container registry, and install Flatpak applications published through your content views.
Prerequisites
- Flatpak is installed on the host. For more information, see Setting up Flatpak.
- Flatpak application repositories are published through content views.
-
Flatpak runtime repositories are available to hosts alongside application repositories. Flatpak applications, such as
rhel9/firefox-flatpak, depend on the runtime for installation. - The Red Hat Flatpak remote is enabled.
- Podman is installed on the host.
- Podman is configured to trust the certificate authority of Satellite Server. For more information, see Section 21.1, “Configuring Podman to trust the certificate authority”.
-
Your Satellite account has the
view_lifecycle_environments,view_products, andview_content_viewspermissions, unless the lifecycle environment allows unauthenticated pull. -
Your Satellite account has a role that grants the
create_personal_access_tokenspermission to generate an access token for authentication. Satellite generates a token automatically when you runpodman login.
Procedure
On the managed host, add your Satellite Server as a Flatpak remote:
$ flatpak remote-add --authenticator-name=org.flatpak.Authenticator.Oci katello oci+https://satellite.example.com/Log in the host to the container registry using one of the following methods:
Certificate authentication
- When registering a host to Satellite or Capsule, select the Set up container registry certs checkbox.
-
If the host is already registered, run the Flatpak - Login to registry via podman job template on the host. Set Set up certificate authentication to
trueand enter the URL of your Capsule as the registry URL.
Using Podman
Log in using Podman:
$ podman login satellite.example.com
Install your application. For example, to install the Mozilla Firefox Flatpak:
$ flatpak install firefox
Additional resources
21.3. Installing Flatpak applications on a host from Capsule Server Copy linkLink copied to clipboard!
Connect your host to the Flatpak remote on Capsule Server, authenticate to the container registry, and install Flatpak applications.
Capsules synchronize Flatpaks and make them available to all hosts, but not organizations, content views, or lifecycle environments. Clients receive the latest Flatpaks synchronized on the Capsule globally.
Prerequisites
- Flatpak repositories are synchronized to Capsule Server. For more information, see Adding lifecycle environments to Capsule Servers by using Satellite web UI in Managing content.
- Flatpak is installed on the host. For more information, see Setting up Flatpak.
-
Flatpak runtime repositories are available to hosts alongside application repositories. Flatpak applications, such as
rhel9/firefox-flatpak, depend on the runtime for installation. - Podman is installed on the host.
- Podman is configured to trust the certificate authority of Capsule Server. For more information, see Section 21.1, “Configuring Podman to trust the certificate authority”.
Procedure
On the managed host, add the Capsule as a Flatpak remote:
$ flatpak remote-add --authenticator-name=org.flatpak.Authenticator.Oci katello oci+https://capsule.example.com/Log in the host to the container registry using one of the following methods:
Certificate authentication
- When registering a host to Capsule, select the Set up container registry certs checkbox.
-
If the host is already registered, run the Flatpak - Login to registry via podman job template on the host. Set Set up certificate authentication to
trueand enter the URL of your Capsule as the registry URL.
Using Podman
Log in using Podman:
$ podman login capsule.example.comYou might need to log in to the registry again if you have not saved your credentials.
Optional: Save your credentials permanently using one of the following options:
To save the credentials for the current user:
$ cp $XDG_RUNTIME_DIR/containers/auth.json $HOME/.config/flatpak/oci-auth.jsonTo save the credentials system-wide:
$ cp $XDG_RUNTIME_DIR/containers/auth.json /etc/flatpak/oci-auth.json
Install your application. For example, to install the Mozilla Firefox Flatpak:
$ flatpak install firefox