RHEL, Fedora, and Flatpaks

posted by Roy Schestowitz on Sep 19, 2026

• Jakub Steiner ☛ Building Flatpaks Locally

  I like to run my Linux as an operating system, so I usually resort to toolbox for packages and development. However flatpak-builder is distributed as a flatpak itself, so here's how you can go about building flatpaks yourself for when GNOME Nighlies are not enough.

  On GNOME OS, some developer tools like git and toolbox are in the base image.

• Christian Hofstede-Kuhn ☛ No Proxmox Backup Client for RHEL? Hold My Container Runtime

  I have a server running Red Hat Enterprise Linux 10 on aarch64, because apparently choosing an enterprise distribution was not enough. I also wanted the architecture to make package availability interesting. I will call it server01 here. Hostnames and repository addresses in the examples and log excerpts are anonymized.

  I also have a Proxmox Backup Server. The goal was simple: back up the machine to PBS, with encryption and incremental uploads, using the infrastructure I already have.

  The missing piece was a convenient native Proxmox Backup Client package for this particular combination of operating system and architecture.

  There was, however, a container image with the client inside it.

  You can probably see where this is going.

• Red Hat ☛ Red Hat OpenShift networking: Default OVN-Kubernetes vs. Cilium operator

  As platform engineering teams scale their Red Hat OpenShift environments to support microservices, Hey Hi (AI) workloads, and declarative multi-cluster management with Cluster API (CAPI), decisions around Container Network Interface (CNI) architecture carry far-reaching consequences. In modern enterprise Kubernetes, networking is the foundation of your cluster's security posture, application performance, and operational visibility.

• Red Hat ☛ Matching OpenShift edge topologies to your physical footprint

  In Red Hat edge platforms: Choosing the right one for your use case, we discussed multiple options with Red Hat Device Edge. Now let's take a closer look at the topologies of Red Hat OpenShift and where each one fits.

• Red Hat ☛ What did Hey Hi (AI) cost you this quarter? [Ed: Slop promotion]

  "What did Hey Hi (AI) cost us this quarter?" That question lands in every platform team's lap eventually, and most teams can't answer it. The CFO isn't trying to be difficult when they ask, but they do need a number, broken down by department, and they need it before the next board meeting.

• Red Hat Official ☛ Beyond OCR: Achieving 98% billing accuracy with GroundX and Red Hat OpenShift AI [Ed: Slop also]

  When a utility provider changes a font or a customer submits a photo of a crumpled bill, these legacy systems break. To solve this, we need to move away from rigid string searches and toward semantic understanding.