home.social

#rhel — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rhel, aggregated by home.social.

  1. Das #Cern spart fast 6 Millionen Euro durch Umstieg von #RHEL auf #Debian, um veraltete Hardware weiterzuverwenden. RHEL 9 und 10 erfordern neue Hardware, die das Cern vermeiden will. Die Umstellung auf Debian 15 ist bis 2030 geplant, aktuell läuft Debian 12. golem.de/news/statt-rhel-cern-

  2. Das #Cern spart fast 6 Millionen Euro durch Umstieg von #RHEL auf #Debian, um veraltete Hardware weiterzuverwenden. RHEL 9 und 10 erfordern neue Hardware, die das Cern vermeiden will. Die Umstellung auf Debian 15 ist bis 2030 geplant, aktuell läuft Debian 12. golem.de/news/statt-rhel-cern-

  3. Das #Cern spart fast 6 Millionen Euro durch Umstieg von #RHEL auf #Debian, um veraltete Hardware weiterzuverwenden. RHEL 9 und 10 erfordern neue Hardware, die das Cern vermeiden will. Die Umstellung auf Debian 15 ist bis 2030 geplant, aktuell läuft Debian 12. golem.de/news/statt-rhel-cern-

  4. Das #Cern spart fast 6 Millionen Euro durch Umstieg von #RHEL auf #Debian, um veraltete Hardware weiterzuverwenden. RHEL 9 und 10 erfordern neue Hardware, die das Cern vermeiden will. Die Umstellung auf Debian 15 ist bis 2030 geplant, aktuell läuft Debian 12. golem.de/news/statt-rhel-cern-

  5. Das #Cern spart fast 6 Millionen Euro durch Umstieg von #RHEL auf #Debian, um veraltete Hardware weiterzuverwenden. RHEL 9 und 10 erfordern neue Hardware, die das Cern vermeiden will. Die Umstellung auf Debian 15 ist bis 2030 geplant, aktuell läuft Debian 12. golem.de/news/statt-rhel-cern-

  6. Infinito.Nexus 12.0: From a Single Server to a Scalable Sovereign Cloud

    Infinito.Nexus 12.0 is one of the most significant releases in the project’s history. Until now, Infinito.Nexus focused primarily on automating complete open-source environments on a single Docker Compose host. Version 12.0 introduces Docker Swarm as a second deployment mode, enabling applications to run across multiple servers, scale horizontally and recover from node failures. This release combines capabilities that are rarely delivered by one automation platform: More than 75 automatically deployable open-source applications One Single Sign-On experience backed by a unified user database Horizontal scaling across multiple cloud servers Automated backup and continuously tested disaster recovery Support across Debian, Arch Linux and RHEL-family distributions Filesystem-independent operation across ext4, btrfs and ZFS Together, these changes transform Infinito.Nexus from an application installer into a comprehensive foundation for scalable, sovereign cloud infrastructure. […]

    blog.infinito.nexus/blog/2026/

  7. PL/SQL, Transact-SQL, , Pro,

    [Forgotten ], Spectra, , , ,

    , , , , "Classic" ,

    , , /#CentOS

    , , , /#Memcached,

    After almost 30 years of technical experience, more than 20 of that professional, I rarely progressed beyond basic proficiency in any I've used.

    I burned out 5 years ago.

  8. #Oracle PL/SQL, #Microsoft Transact-SQL, #Access, #FileMaker Pro, #MySQL

    [Forgotten #CMS], #Allaire Spectra, #MSCMS, #SharePoint, #Drupal, #WordPress

    #HTML, #CSS, #JavaScript, #ColdFusion #CFML, "Classic" #ASP, #PHP

    #Windows, #MacOS, #RHEL/#CentOS

    #IIS, #Apache, #NGNIX, #Memcache/#Memcached, #Varnish

    After almost 30 years of technical experience, more than 20 of that professional, I rarely progressed beyond basic proficiency in any #technology I've used.

    I burned out 5 years ago.

  9. #Oracle PL/SQL, #Microsoft Transact-SQL, #Access, #FileMaker Pro, #MySQL

    [Forgotten #CMS], #Allaire Spectra, #MSCMS, #SharePoint, #Drupal, #WordPress

    #HTML, #CSS, #JavaScript, #ColdFusion #CFML, "Classic" #ASP, #PHP

    #Windows, #MacOS, #RHEL/#CentOS

    #IIS, #Apache, #NGNIX, #Memcache/#Memcached, #Varnish

    After almost 30 years of technical experience, more than 20 of that professional, I rarely progressed beyond basic proficiency in any #technology I've used.

    I burned out 5 years ago.

  10. #Oracle PL/SQL, #Microsoft Transact-SQL, #Access, #FileMaker Pro, #MySQL

    [Forgotten #CMS], #Allaire Spectra, #MSCMS, #SharePoint, #Drupal, #WordPress

    #HTML, #CSS, #JavaScript, #ColdFusion #CFML, "Classic" #ASP, #PHP

    #Windows, #MacOS, #RHEL/#CentOS

    #IIS, #Apache, #NGNIX, #Memcache/#Memcached, #Varnish

    After almost 30 years of technical experience, more than 20 of that professional, I rarely progressed beyond basic proficiency in any #technology I've used.

    I burned out 5 years ago.

  11. #Oracle PL/SQL, #Microsoft Transact-SQL, #Access, #FileMaker Pro, #MySQL

    [Forgotten #CMS], #Allaire Spectra, #MSCMS, #SharePoint, #Drupal, #WordPress

    #HTML, #CSS, #JavaScript, #ColdFusion #CFML, "Classic" #ASP, #PHP

    #Windows, #MacOS, #RHEL/#CentOS

    #IIS, #Apache, #NGNIX, #Memcache/#Memcached, #Varnish

    After almost 30 years of technical experience, more than 20 of that professional, I rarely progressed beyond basic proficiency in any #technology I've used.

    I burned out 5 years ago.

  12. Package management is one of those things every Linux admin should know cold.

    Search for a package: dnf search packagename
    Install it: dnf install packagename
    Check what's installed: rpm -qa | grep packagename
    Remove it cleanly: dnf remove packagename

    Your package manager is your best friend. Treat it accordingly.
    #Linux #SysAdmin #PackageManagement #TechTip #RHEL

  13. #TechTipThursday
    Package management is one of those things every Linux admin should know cold.

    Search for a package:
    dnf search packagename

    Install it:
    dnf install packagename

    Check what's installed:
    rpm -qa | grep packagename

    Remove it cleanly:
    dnf remove packagename

    Your package manager is your best friend. Treat it accordingly.
    #Linux #SysAdmin #PackageManagement #TechTip #RHEL #RockyLinux

  14. This week's Linux and FOSS news:

    LINUX NEWS

    Q4OS will do whatever Debian does regarding age attestation/verification:
    q4os.org/forum/viewtopic.php?i

    Linux Mint 23 Getting New Cinnamon Screenshots Tool, Network Improvements:
    9to5linux.com/linux-mint-23-ge

    openSUSE Releases Agama 21 Installer with Better Network Management:
    9to5linux.com/opensuse-release

    Ubuntu Core 26 cuts OTA update size, enables ARM64 Livepatch:
    omgubuntu.co.uk/2026/05/ubuntu

    Fedora Pulls the Plug on Deepin Over Security and Maintenance Failures:
    feed.itsfoss.com/link/24361/17

    Nitrux 6.1 Is Now Available for Download, Powered by Linux Kernel 7.0:
    9to5linux.com/nitrux-6-1-is-no

    Mageia 10 RC1 available with new artwork, updated packages:
    blog.mageia.org/en/2026/05/19/

    Tails 7.8 Anonymous Linux OS Patches Recent Kernel Flaws, Removes Thunderbird:
    9to5linux.com/tails-7-8-anonym

    Red Hat Enterprise Linux 10.2 Released with Optional Command-Line AI Assistant:
    9to5linux.com/red-hat-enterpri

    AlmaLinux to Unveil Media & Entertainment Edition at AlmaLinux Day on July 18th:
    9to5linux.com/almalinux-to-unv

    This Week in Plasma: Xe Driver Support and Polishing Discover:
    blogs.kde.org/2026/05/23/this-

    Phosh 0.55.0 released with new Syncthing quick setting, Phoc updated wlroots 0.20.0, various bug fixes and improvements:
    phosh.mobi/releases/rel-0.55.0/

    GNOME Commander 2.0 Released Following Rewrite In Rust & GTK4:
    phoronix.com/news/GNOME-Comman

    Bazaar 0.8.1 Fixes Flatpak Update Glitches and Tightens GNOME App Store UI:
    linuxcompatible.org/story/baza

    "AM" AppImage Manager 10.2.1 Fixes Desktop File Mess and Catches Typos Before They Happen:
    linuxcompatible.org/story/am-1

    Shelly 2.3.1 GUI Package Manager for Arch Linux Improves Notifications:
    9to5linux.com/shelly-2-3-1-gui

    (more Linux and FOSS news in comments)

    #WeeklyNews #News #Linux #LinuxNews #Q4OS #LinuxMint #openSUSE #Ubuntu #UbuntuCore #Fedora #Nitrux #Mageia #Mageia10 #Tails #TailsOS #RHEL #RHEL102 #AlmaLinux #KDE #KDEPlasma #Phosh #GNOMECommander #Bazaar #AppImageManager #Shelly #SoftwareStore #MobileLinux #LinuxMobile #DesktopLinux #LinuxDesktop #DistroRelease #DesktopEnvironment #FosseryTech

  15. Archivierung und Kompression mit tar: Grundlagen, Optionen und Beispiele

    tar (Tape Archiver) ist das Standard-Archivierungswerkzeug unter Linux, das mehrere Dateien und Ordner zu einem einzigen Archiv bündelt. Im Gegensatz zu gzip, bzip2 und xz komprimiert tar nicht selbst, sondern arbeitet mit Kompressionstools zusammen (z, j, J). Es erhält vollständige Metadaten inklusive Berechtigungen und SELinux-Kontexte. Wichtige Optionen von tar -c (create) : Erstellt ein neues Archiv. -f (file name). : Gibt den Dateinamen des Archivs an. # Einen Ordner […]

    andreas-moor.de/archivierung-u

  16. Kompression mit zip: Grundlagen, Optionen und Beispiele

    zip ist das universellste Archivierungs- und Kompressionswerkzeug, das unter Linux, Windows und macOS funktioniert. Es kombiniert Archivierung und Kompression in einem Schritt und kann Ordner direkt verarbeiten – im Gegensatz zu gzip, bzip2 und xz. Ideal für plattformübergreifenden Dateiaustausch. Wichtige Optionen von zip -r : Rekursiv: Komprimiert Ordner und alle Unterordner (einzigartig bei zip). zip -r backup.zip ordner/ -d oder unzip : Entpackt eine .zip-Datei. unzip ist ein […]

    andreas-moor.de/kompression-mi

  17. This week's Linux and FOSS news:

    LINUX NEWS

    Ubuntu LTS Releases Now Get 15 Years of Support:
    omgubuntu.co.uk/2025/11/ubuntu

    Ubuntu's Rust Transition Hits Another Bump as sudo-rs Security Vulnerabilities Show Up:
    itsfoss.com/news/sudo-rs-issue

    Nitrux 5.0.0 Released: A 'New Beginning' That's Not for Everyone (By Design):
    itsfoss.com/news/nitrux-5-rele

    MX Linux 25 'Infinity' arrives with a cleaner look and easier installation:
    betanews.com/2025/11/11/mx-lin

    Debian 13.2 Released With Dozens Of Fixes:
    phoronix.com/news/Debian-13.2-

    Tails 7.2 brings Tor Browser 15.0, Linux 6.12 LTS kernel, privacy upgrades, and more:
    alternativeto.net/news/2025/11

    Red Hat's RHEL 10.1 Released With systemd Soft-Reboots, Easier AI Accelerator Drivers:
    phoronix.com/news/Red-Hat-Ente

    SparkyLinux 8.1 released with updated software and desktop environments:
    alternativeto.net/news/2025/11

    GNOME's Nautilus File Manager Finally Supporting Ctrl+Insert & Shift+Insert:
    phoronix.com/news/GNOME-Nautil

    KDE Plasma 6.6 to get a great new feature - limit virtual desktops to the primary screen:
    gamingonlinux.com/2025/11/kde-

    Plasma 6.6 Will Avoid Running Out Of RAM When Something Crashes In A Loop:
    phoronix.com/news/Plasma-6.6-B

    Budgie 10.9.4 adds libpeas2 support, ABI bumps, and Raven plugin changes:
    alternativeto.net/news/2025/11

    Miracle-WM Adds Accessibility, Touchpad & Animation Options:
    omgubuntu.co.uk/2025/11/miracl

    Linux’s Slickest System Monitor App (Mission Center) Gets Updated:
    omgubuntu.co.uk/2025/11/missio

    Maemo Leste status report: system ported to Devuan Daedalus, new CI/CD, updated browser, calendar and chat app, improved hardware support, etc.:
    maemo-leste.github.io/maemo-le

    (more Linux and FOSS news in comments)

    #WeeklyNews #News #Linux #LinuxNews #Ubuntu #Nitrux #MXLinux #Debian #Tails #TailsOS #RHEL #SparkyLinux #GNOME #KDE #KDEPlasma #Budgie #Miracle_wm #MaemoLeste #MobileLinux #LinuxMobile #LinuxDesktop #DesktopLinux #LinuxDistro #DistroRelease #DesktopEnvironment #FosseryTech

  18. Rocky Linux 10, based on RHEL 10, released

    Following the release of the Red Hat Enterprise Linux 10 and the AlmaLinux 10, yet another Red Hat-based Linux derivative distro, Rocky Linux, has just released a new version that is compatible with the tenth major version of RHEL. This sets a huge milestone for just another community version of the RHEL distribution. You can download this version of Rocky Linux here.

    Download now

    Rocky Linux 10, just like RHEL 10, requires the x86_64-v3 processor in order to run on modern computers. This is unlike AlmaLinux 10 that needed at least the x86_64-v2 processor. Also, Rocky Linux 10 no longer ships the 32-bit packages, which means that you will no longer to run 32-bit applications.

    For the desktop environment, this version of Rocky Linux now uses the Wayland server exclusively instead of the legacy X11 protocol. However, some of the applications that have not yet been ported to Wayland can now run using the Xwayland protocol.

    This version of Rocky Linux now supports the RISC-V architecture for users with such processor architecture. This is to make sure that computers that use a RISC-V processor be able to use Rocky Linux for the first time, expanding hardware support to the broader audience.

    The following architectures are supported:

    • 64-bit AMD/Intel x86-64-v3 (x86_64)
    • 64-bit RISC-V (riscv64)
    • 64-bit ARMv8.0-A (aarch64)
    • IBM POWER, little endian (ppc64le)
    • IBM z (s390x)

    The following common packages have been updated:

    • Dynamic programming languages, web, and database servers
      • PHP 8.3
      • Python 3.12
      • nginx 1.26
      • PostgreSQL 16.8
      • MySQL 8.4
      • Valkey 8.0
      • MariaDB 10.11
    • Performance tools and debuggers
      • GDB 14.2
      • Valgrind 3.23.0
      • SystemTap 5.1
      • Dyninst 12.3.0
      • elfutils 0.192
      • libabigail 2.6
    • Performance monitoring tools
      • Performance Co-pilot 6.3.0
      • Grafana 10.2.6
    • Compiler toolsets
      • LLVM Toolset 19.1.7
      • Rust Toolset 1.84.1
      • Go Toolset 1.23

    Download Rocky Linux 10 to improve your user experience!

    #Linux #LinuxDistro #news #redHat #RedHatEnterprise #RedHatEnterpriseLinux #RHEL #RHEL10 #Rocky #RockyLinux #RockyLinux10 #Tech #Technology #update

  19. Manage your Linux systems like a container!

    I’ve got to tell you, I have not been so excited about a technology… probably since Containers. At Summit this year Red Hat announced the General Availability of Image Mode for RHEL. So I got to spend a week in Boston, explaining, over and over again, why that’s important.

    See, Image mode is kind of a big deal. It takes container workflows, and applies it to your data center servers using a technology called bootc. This concept isn’t new exactly, this sort of technology has been applied to edge devices, and phones, and other appliances for years. But what we have now is a general purpose linux that you can update using a bootable container image. This changes things.

    So think about a Linux system as you know it today. We’re calling that Package Mode now in order to avoid confusion. RHEL Package Mode is a Linux base, with a package manager, where you install and configure things, and then fight to keep those things from drifting pretty much from then until eternity. There’s a whole facet of the IT industry around mitigating that drift. Package and config management is a huge business! For good reason! Drift is what makes your routine 2AM maintenance into a panic attack when the database server doesn’t come back up.

    So I talked a lot about Image Mode at Summit, but I have to admit, I hadn’t touched it yet! So Now that I’m back home, and my time is a little less all consumed by prep for the RHEL 10 release, and Summit deadlines, I decided to take some time and get hands on with this revolutionary thing.

    Building a pipeline

    So, I use Gitlab community edition as a repository for a few container builds I maintain. Some time back I managed to get the CI/CD pipelines working for my container builds. These were nothing fancy, but they work. I commit a change to the repository, and a job kicks off to rebuild the container, and push it into a registry. In some cases that’s just the internal Gitlab registry, in others its Docker Hub. I, of course, do it all with Podman. So when I decided to tackle Image Mode, I thought it would be best to just rip that band-aid right off and do it in Gitlab, and have the builds happen there. How hard could it be? I already had container builds running there!

    So I made a repo, and copied my CI config from one of the container builds that just used podman and the local registry, and threw in a basic Containerfile that just sourced FROM the RHEL bootc base image, and then did a package install. Commit, sit back in my arrogance and wait for my image.

    It failed. For reasons I still don’t fully understand, the container build uses fuse-overlayfs to do its build, and couldn’t in my runner’s podman in podman build container. I did some research, and luckily I have access to internal Red Hat knowledge, so I was able to bounce some ideas around and came up with a solution. Two things actually. My runner needed some config changes. Here, I’ll share them with you.

    Here is my Runner config

    [[runners]]  name = "dind-container"  url = "https://git.undrground.org"  id = 3  token = "NoTokenForYou"  token_obtained_at = somedatestamp  token_expires_at = someotherdatestamp  executor = "docker"  environment = ["FF_NETWORK_PER_BUILD=1"]  [runners.cache]    MaxUploadedArchiveSize = 0    [runners.cache.s3]    [runners.cache.gcs]    [runners.cache.azure]  [runners.docker]    tls_verify = false    image = "docker:git"    privileged = true    disable_entrypoint_overwrite = false    oom_kill_disable = false    disable_cache = false    volumes = ["/cache"]    shm_size = 0    network_mtu = 0

    The things I had to add were, first, privileged = true. This gives the container the access it needs to do its fusefs work. And the environment “FF_NETWORK_PER_BUILD=1”, which I believe tweaks the podman networking such that it fixed a DNS resolution problem I was having in my builds.

    With that fixed, I was able to get builds working! I have two things to share that may help you if you are trying to do the same. First, another Red Hatter built a public example repo that will apparently “just work” if you use it as a base for your Image Mode CI/CD. It didn’t work for me, but I suspect that was more about my gitlab setup and less about the functionality of the example. You can find that example, Here. What I ended up doing was modify my existing podman CI file. That looks like this:

    ---image: registry.undrground.org/gangrif/podman-builder:latest#services:#    - docker:dindbefore_script:    - dnf -y install podman git subscription-manager buildah skopeo podman    - subscription-manager register --org=${RHT_ORGID} --activationkey=${RHT_ACT_KEY}    - subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms --enable rhel-9-for-x86_64-baseos-rpms    - export REVISION=$(git rev-parse --short HEAD)    - podman login --username gitlab-ci-token --password $CI_JOB_TOKEN      $CI_REGISTRY    - podman login --username $RHLOGIN --password "$RHPASS" registry.redhat.ioafter_script:    - podman logout $CI_REGISTRY    - subscription-manager unregisterstages:    - buildcontainerize:    stage: build    script:      .    - podman build --secret id=creds,src=/run/containers/0/auth.json --build-arg GIT_HASH=$CI_COMMIT_SHA      -t $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA -t $CI_REGISTRY_IMAGE:latest       .    - podman push $CI_REGISTRY_IMAGE

    Now, this example contains no verification or validation, so I suggest you maybe look into the proper example linked externally. That one has a lot of testing included. Mine will improve with time. 😉

    Registry Authentication for your build

    Now, there’s a few things to note here. First, Notice that I am not just logging into my own registry, but registry.redhat.io. You register using your Red Hat login for the Red Hat private registry, and that’s where the bootc base images come from. I also use subscription-manager to register the build container to Red Hat’s CDN. That’s because the RHEL Image Mode build is building RHEL, and must be done using an entitled host in order to receive any updates or packages during the container build. This was something I had gotten stuck on for some time, its a little tough to wrap your head around. Once you do though, it makes sense.

    Authenticating your bootc system with your registry, automatically

    I am also passing the podman authentication token file into a podman secret at build time. This is important later. If your bootc images are stored in a registry that is not public, you will need to authenticate to that registry in order to pull your updated images after deployment. The easiest way to bake in that authentication is to simply take the authentication from the build host, and place it into the built image. There is some trickery that happens in your Containerfile to make this work. You can read more about this here.

    Containerfile

    So, I told you we build image mode like a container. I meant it. We literally write a Contanerfile, and source it from these special bootc images that are published by Red Hat. There are a few things you’ll want to think about when building a bootc Containerfile vs a standard application container. Things that you wouldn’t normally think about when building a normal container.

    Content

    First, RHEL is entitled software, that doesn’t change for RHEL Image Mode. This is pretty seemless if you are doing your build directly on an Entitled RHEL system. But if you’re in a ubi container like I am, you’ll need to subscribe the UBI container because the BootC build will depend on that entitlement to enable its own repositories. That is not true, however, for 3rd party public repositories. Those just get enabled right inside of the Containerfile. This sounds confusing, but it boils down to this. RHEL repository? Entitled by the build host, Other repository? Add it via the Containerfile. I add EPEL in my example below.

    Users

    Something else I don’t usually see done in a standard container is the addition of users. Remember this is going to be a full RHEL host at the other end, so you might need to add users. In my case I am adding a local “breakglass” user, because I am leveraging IdM for my identities. But if something goes wrong during the provisioning, i want a user I can login to the system with to troubleshoot. You can also come in later with other tools to add users. You can enable cloud-init and add them there, or if you are using the image builder tool I’ll talk about in a bit, you can give it a config.toml file to add users at that point.

    Other Considerations

    Other things that you’ll need to think about might be firewall rules, container registry authentication, and even the lack of an ENTRYPOINT or CMD. Because this system is expected to boot into a full OS, it is not going to run a single dedicated workload. Instead you’ll be enabling services like you would on a standard RHEL system, with systemctl.

    My Containerfile

    Now that we’re through all of that, let me show you what I ended up with as a Containerfile.

    FROM registry.redhat.io/rhel9/rhel-bootc:latest# Enable EPEL, install updates, and install some packagesRUN dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpmRUN dnf -y updateRUN dnf -y install ipa-hcc-client rhc rhc-worker-playbook cloud-init && dnf clean all# This sets up automatic registration with Red Hat InsightsCOPY --chmod=0644 rhc-connect.service /usr/lib/systemd/system/rhc-connect.serviceCOPY .rhc_connect_credentials /etc/rhc/.rhc_connect_credentialsRUN systemctl enable rhc-connect && touch /etc/rhc/.run_rhc_connect_next_boot# This is my backdoor user, in case of IdM join failureRUN useradd breakglassRUN usermod -p '$6$s0m3pAssw0rDHasH' breakglassRUN groupmems -g wheel -a breakglass# This picks up that podman pull secret, and adds it to the build imageCOPY link-podman-credentials.conf /usr/lib/tmpfiles.d/link-podman-credentials.confRUN --mount=type=secret,id=creds,required=true cp /run/secrets/creds /usr/lib/container-auth.json && \    chmod 0600 /usr/lib/container-auth.json && \    ln -sr /usr/lib/container-auth.json /etc/ostree/auth.json# This configures the bootc update timer to run at a time that I consider acceptableRUN mkdir -p /etc/systemd/system/bootc-fetch-apply-updates.timer.d/COPY weekly-timer.conf /etc/systemd/system/bootc-fetch-apply-updates.timer.d/weekly.conf

    You can see from my comments what’s going on in the various blocks in that Containerfile. My intention is to use this as a base RHEL system, and then make more derivative images based on this one. For instance, if I wanted a web server, I would base a new Containerfile on this image, and then add in a RUN dnf install httpd. Its important to note that you shouldn’t be installing packages on these deployed systems after they are up and running. Those installations should happen in the image. If you install a package on a running image mode system, that change will not be carried into the next image update on your system unless you then incorporate it into your bootable container image. This means that you will need to plan ahead, but it also means that tracking package drift in the future is a thing of the past!

    In my case, the above mentioned CI automation, and this Containerfile worked in my Gitlab instance, with the above Runner modifications. The build job will take some time, a bootc image is much larger than the lightweight container images you are used to if you’ve been building application containers.

    But what about turning that into a VM?

    So I am covering but ONE method of getting this image deployed to an acutal system. You can use a myriad of different methods including Kickstart, writing an ISO, PXEBOOT, but what I am doing (because it suits my needs) is turning my image into a qcow2 file, which is a virtual disk image for use with Libvirt. If you’re familiar with Image Builder, the tool used to churn out tailored RHEL disk images, then this wont be a surprise. Theres a container that you can grab that just runs image builder, you give it a bootable container image, and it turns it into a qcow2! Ive cooked up a script that pulls my bootable container right from my registry, writes it to a qcow2, then immediately passes that to virt-install and builds a VM out of it!

    In my case, it also uses cloud-init to set its hostname, auto registers, and connects to insights, and then uses a slick new tech preview feature that auto-joins my lab’s IdM domain through insights! Here is my script:

    #!/bin/bashVMNAME=$1podman login --username my-gitlab-username -p 'gitlab-token' registry.undrground.orgpodman login --username my-redhat-login -p 'redhatpassword registry.redhat.iopodman pull registry.undrground.org/gangrif/rhel9-imagemode:latestsudo podman run \    --rm \    -it \    --privileged \    --pull=newer \    --security-opt label=type:unconfined_t \    -v $(pwd)/config.toml:/config.toml \    -v $(pwd)/output:/output \    -v /var/lib/containers/storage:/var/lib/containers/storage \    registry.redhat.io/rhel9/bootc-image-builder:latest \    --type qcow2 \    registry.undrground.org/gangrif/rhel9-imagemode:latestcat << EOF > $VMNAME.init#cloud-configfqdn: $VMNAME.idm.undrground.orgEOFmv $(pwd)/output/qcow2/disk.qcow2 /var/lib/libvirt/images/$VMNAME-disk0.qcow2virt-install \--name $VMNAME \--memory 4096 \--vcpus 2 \--os-variant rhel9-unknown \--import \--clock offset=localtime \--disk=/var/lib/libvirt/images/$VMNAME-disk0.qcow2 \-w bridge=bridge20-lab \--autoconsole none \--cloud-init user-data=$VMNAME.init 

    This, of course, can be improved, but as a proof of concept it works great! Ive build a few test systems and so far its working flawlessly! Now, when I wans to update my systems, I update the gitlab repository with the changes, and let the CI run. Then once it completes, all I do is run this script to make a new vm! The running vms -should- (i have not tested this yet) get the updated bootble container image from the registry on saturday at 3AM, and reboot if new changes are applied.

    Wrapping it up

    This is, i think, the thing we’ve been promised for years. Ever since the advent of the cloud when we were told that we should stop treating our servers like pets, but never really given a clear definition of how. Image Mode makes that promise a reality. I’m certain I’ll be sharing more as my Image Mode journey progresses. Thanks for reading!

    #bootc #cloud #image #imageMode #linux #redHat #redHatEnterpriseLinux #rhel #services

  20. @carlwgeorge @jbouter This is what I do at $DAYJOB, where I'm implementing for anything that won't use or doesn't have annoying validation requirements on RHEL minor versions. Which means everything for now until we actually make the RHEL purchase 😅 Waiting on the final sign off from the higher ups on that...

    Using tools like +#Katello (upstream of ) to handle system and content lifecycles makes life stupid simple in ensuring matching environments.

  21. AND WE CAN MAKE SUBSCRIPTION ALLOCATIONS NOW

    For those that don't know what that means, it allows you to import your subscriptions directly into Foreman+Katello (Red Hat Satellite) rather than having to configure your own local mirror to do so.

  22. :tux: Red Hat gibt Red Hat Enterprise Linux 7.7 frei

    📌 Red Hat hat Enterprise Linux 7.7 freigegeben. Es ist die letzte Ausgabe von RHEL 7, die neue Funktionalität ausliefert.

    #RedHat #Linux #RedHatEnterprise #EnterpriseLinux77 #RHEL #RHEL7

    pro-linux.de/news/1/27325/red-