13장. Managing Flatpak repositories in Satellite


Flatpak allows users to install, manage, and run portable applications on Satellite, primarily for desktop environments. In Satellite, you can integrate Flatpak repositories to distribute and control Flatpak applications across managed hosts. By configuring Flatpak repositories, you ensure that systems have access to the necessary application packages while maintaining centralized control over application deployment.

Flatpak repositories function similarly to other content repositories in Satellite. You can synchronize, manage access permissions, and assign repositories to specific lifecycle environments to control which applications are available to systems. You can also use Hammer CLI to manage Flatpak repositories.

For more information, see Installing applications using Flatpak.

13.1. Enabling the Flatpak remote

This procedure configures and manages Flatpak repositories by using Hammer CLI.

Prerequisites

  • Your Satellite account has a role that grants the permissions view_flatpak_remotes, create_flatpak_remotes, edit_flatpak_remotes, and destroy_flatpak_remotes.
  • Set up Flatpak. For more information, see Setting up Flatpak.
  • Flatpak applications rely on Flatpak runtimes. For example, rhel9/firefox-flatpak depends on rhel9/flatpak-runtime.
  • Ensure that runtime repositories are available to clients alongside application repositories for installations to work.

CLI procedure

  1. Enable a Flatpak remote on the Satellite Server by using standalone Red Hat Enterprise Linux systems or Red Hat Satellite:

    $ hammer flatpak-remote create \
    --name=My_Flatpak_Remote_Name \
    --organization=My_Organization \
    --url=My_Flatpak_Remote_URL

    You can include authentication details by using the options --username=My_User_Name --token=My_Token.

    You can generate a Red Hat official token at Registry Service Accounts.

  2. Update the Flatpak remote with authentication credentials:

    $ hammer flatpak-remote update \
    --id My_Flatpak_Remote_ID \
    --token=My_Token \
    --username=My_User_Name
  3. Optional: List and view information about the Flatpak remote:

    $ hammer flatpak-remote list
    $ hammer flatpak-remote info --id My_Flatpak_Remote_ID
  4. Scan the Flatpak remote:

    $ hammer flatpak-remote scan --id=My_ID
  5. List repositories in the Flatpak remote:

    $ hammer flatpak-remote remote-repository list --flatpak-remote-id=My_ID
  6. Mirror a Flatpak remote repository to a Satellite product:

    $ hammer flatpak-remote remote-repository mirror \
    --id=My_Remote_Repo_ID \
    --product-id=Satellite_Product_ID

    The --id in this command refers to the Flatpak remote repository ID, not the standard Satellite repository ID.

    You can view the repository under the selected product in Satellite web UI. Set the Include Tags field to latest.

  7. Synchronize the Satellite repository:

    $ hammer repository sync --id=My_Repo_ID

    The --id in this command refers to the standard Satellite repository ID, not the Flatpak remote repository ID.

Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 문서 정보

Legal Notice

Theme

© 2026 Red Hat
맨 위로 이동