#bootc — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #bootc, aggregated by home.social.
-
@zak So. I’m at the Red Hat Summit this week and there is discussion about something you might be interested in.
bootc (the main tool for RHEL Image Mode) allows you to basically create your own immutable OS image. It’s sort of like… rolling your own distro but using tools similar to creating docker container images rather than compiling from scratch.
The intent is of course virtualization - but you can deploy them on bare metal.
https://docs.fedoraproject.org/en-US/bootc/bare-metal/
It may be a heavier lift than you want to mess with - but it’s pretty interesting nonetheless.
-
Fascinating idea, though I can’t help but think it would just become some sort of attack vector of its own.
Also given the push towards immutable distros (which is a good and cool idea) I’d be very curious how this could actually be implemented.
#linux #copyfail #killswitch #kernel #immutable #imagemode #bootc
-
Alongside the Fedora 44 release, I’m happy to announce that we have sealed bootable container images ready for testing for the Fedora Atomic Desktops!
Sealed bootable container images include all the components needed to create a fully verified boot chain, from the firmware to the operating system composefs image. This relies on Secure Boot on UEFI systems.
More details at https://fedoramagazine.org/sealed-atomic-desktops-test-images/ and https://github.com/travier/fedora-atomic-desktops-sealed
#Fedora #AtomicDesktops #Silverblue #Kinoite #bootc #composefs
-
Fedora 44 has been released! 🎉
You can catch up with all the changes for the Atomic Desktops in the usual What's new article in the Fedora Magazine: https://fedoramagazine.org/whats-new-fedora-atomic-desktops-in-fedora-linux-44/
#Fedora #AtomicDesktops #Silverblue #Kinoite #SwayAtomic #BudgieAtomic #COSMICAtomic #bootc
-
New Fedora Podcast episode!! 🎙️
What does bootc actually look like when it's running in production? James Harmison joins us to talk about building custom bootc images across wildly different contexts: NVIDIA drivers, AGX Orin hardware, replacing RHCOS in OpenShift, and even a couch gaming rig.
Real world. Real use cases. No lab bubbles.🎧 podcast.fedoraproject.org
#Fedora #Linux #bootc #OpenSource #Containers #OpenShift -
New Fedora Podcast episode!! 🎙️
What does bootc actually look like when it's running in production? James Harmison joins us to talk about building custom bootc images across wildly different contexts: NVIDIA drivers, AGX Orin hardware, replacing RHCOS in OpenShift, and even a couch gaming rig.
Real world. Real use cases. No lab bubbles.🎧 podcast.fedoraproject.org
#Fedora #Linux #bootc #OpenSource #Containers #OpenShift -
New Fedora Podcast episode!! 🎙️
What does bootc actually look like when it's running in production? James Harmison joins us to talk about building custom bootc images across wildly different contexts: NVIDIA drivers, AGX Orin hardware, replacing RHCOS in OpenShift, and even a couch gaming rig.
Real world. Real use cases. No lab bubbles.🎧 podcast.fedoraproject.org
#Fedora #Linux #bootc #OpenSource #Containers #OpenShift -
New Fedora Podcast episode!! 🎙️
What does bootc actually look like when it's running in production? James Harmison joins us to talk about building custom bootc images across wildly different contexts: NVIDIA drivers, AGX Orin hardware, replacing RHCOS in OpenShift, and even a couch gaming rig.
Real world. Real use cases. No lab bubbles.🎧 podcast.fedoraproject.org
#Fedora #Linux #bootc #OpenSource #Containers #OpenShift -
New Fedora Podcast episode!! 🎙️
What does bootc actually look like when it's running in production? James Harmison joins us to talk about building custom bootc images across wildly different contexts: NVIDIA drivers, AGX Orin hardware, replacing RHCOS in OpenShift, and even a couch gaming rig.
Real world. Real use cases. No lab bubbles.🎧 podcast.fedoraproject.org
#Fedora #Linux #bootc #OpenSource #Containers #OpenShift -
I've been slowly working through a modernization of my web host.
I rent a server on hetzner, and up until now its primarily been a container host. but I basically manually manage it. Services in containers, and running under quadlet, but their management has been a bit of a burden.
Recently I ordered another Hetzner system, and this time I had them give me a console, and I manually reinstalled it on RHEL Image Mode (bootc).
On top of that I decided it was time to automate. One at a time I am re-creating my pods using ansible. At the end of this, i should have a largely immutable system, thats easy to keep up to date, and all my services are nicely defined as code.
-
Damned, right after I got my first #rhel 10 #microshift image mode iso done, the rugged box won't accept any of my usb sticks as boot device. Just stays in boot screen. It's a nice old dell3200 box. Can one start #bootc install with kexec?
-
Damned, right after I got my first #rhel 10 #microshift image mode iso done, the rugged box won't accept any of my usb sticks as boot device. Just stays in boot screen. It's a nice old dell3200 box. Can one start #bootc install with kexec?
-
Damned, right after I got my first #rhel 10 #microshift image mode iso done, the rugged box won't accept any of my usb sticks as boot device. Just stays in boot screen. It's a nice old dell3200 box. Can one start #bootc install with kexec?
-
Damned, right after I got my first #rhel 10 #microshift image mode iso done, the rugged box won't accept any of my usb sticks as boot device. Just stays in boot screen. It's a nice old dell3200 box. Can one start #bootc install with kexec?
-
Damned, right after I got my first #rhel 10 #microshift image mode iso done, the rugged box won't accept any of my usb sticks as boot device. Just stays in boot screen. It's a nice old dell3200 box. Can one start #bootc install with kexec?
-
secureblue @[email protected] now contains bazaar! I'm very happy to see consistent and good store among many bootc images, leaving the old PackageKit slow store behind! Shoutout to @kolunmi@kolunmi@hachyderm.io
https://github.com/secureblue/secureblue/releases/tag/v4.8.1
#bazaar #secureblue #bootc -
#OpenSource developers, we are looking for speakers for #DevConf_CZ 2026! 🐧
One of the highlights this year will be the evolution of #Linux operating systems. If you have insights on #CentOS, #Fedora, #Silverblue, or advancements in #Kernel development and #Edge computing, we invite you to submit your proposals: https://pretalx.devconf.info/devconf-cz-2026/cfp
-
We continuously update the map with existing Desktop Linux use cases on our website at https://eu-os.eu/use-cases#notable-migrations. Today, we added two new places:
1) 🇳🇱 The university of Groningen offers Linux computers to their staff if they ask for it. https://ukrant.nl/magazine/we-can-do-without-them-how-the-ug-is-cutting-ties-with-big-tech/?lang=en
2) 🇨🇿 The Czech National Film Archive uses a similat setup to #EU_OS: #AlmaLinux #bootc with #freeIPA for some of their staff. Now Czechia is on the map! https://nfa.cz/en
-
We continuously update the map with existing Desktop Linux use cases on our website at https://eu-os.eu/use-cases#notable-migrations. Today, we added two new places:
1) 🇳🇱 The university of Groningen offers Linux computers to their staff if they ask for it. https://ukrant.nl/magazine/we-can-do-without-them-how-the-ug-is-cutting-ties-with-big-tech/?lang=en
2) 🇨🇿 The Czech National Film Archive uses a similat setup to #EU_OS: #AlmaLinux #bootc with #freeIPA for some of their staff. Now Czechia is on the map! https://nfa.cz/en
-
We continuously update the map with existing Desktop Linux use cases on our website at https://eu-os.eu/use-cases#notable-migrations. Today, we added two new places:
1) 🇳🇱 The university of Groningen offers Linux computers to their staff if they ask for it. https://ukrant.nl/magazine/we-can-do-without-them-how-the-ug-is-cutting-ties-with-big-tech/?lang=en
2) 🇨🇿 The Czech National Film Archive uses a similat setup to #EU_OS: #AlmaLinux #bootc with #freeIPA for some of their staff. Now Czechia is on the map! https://nfa.cz/en
-
We continuously update the map with existing Desktop Linux use cases on our website at https://eu-os.eu/use-cases#notable-migrations. Today, we added two new places:
1) 🇳🇱 The university of Groningen offers Linux computers to their staff if they ask for it. https://ukrant.nl/magazine/we-can-do-without-them-how-the-ug-is-cutting-ties-with-big-tech/?lang=en
2) 🇨🇿 The Czech National Film Archive uses a similat setup to #EU_OS: #AlmaLinux #bootc with #freeIPA for some of their staff. Now Czechia is on the map! https://nfa.cz/en
-
We continuously update the map with existing Desktop Linux use cases on our website at https://eu-os.eu/use-cases#notable-migrations. Today, we added two new places:
1) 🇳🇱 The university of Groningen offers Linux computers to their staff if they ask for it. https://ukrant.nl/magazine/we-can-do-without-them-how-the-ug-is-cutting-ties-with-big-tech/?lang=en
2) 🇨🇿 The Czech National Film Archive uses a similat setup to #EU_OS: #AlmaLinux #bootc with #freeIPA for some of their staff. Now Czechia is on the map! https://nfa.cz/en
-
Fedora's elections are now open until Wednesday, 7th January!
I'm applying for a seat at FESCo [1] as I want to represent the interests of users, developers and maintainers of what we call Atomic, Bootable Container, Image Based or Immutable variants of Fedora (CoreOS, Atomic Desktops, IoT, bootc, etc.).
You can find my full interview at https://communityblog.fedoraproject.org/f43-fesco-elections-siosm/
And vote at https://elections.fedoraproject.org/
-
And because my week's been so busy, here I am, after hours, working on my demo for TOMORROW's Into the Terminal.
Want to see how it turns out? Itll either be awesome, or a trainwreck. Either way, entertainment at its finest!
-
Holger from @b1systems, partner of #EU_OS, speaks tomorrow (Thursday 11 Dec) at #OSXP 2025 in Paris about #LinuxOnTheDesktop. If you are in Paris, don't miss this session!
Conference Programme: https://www.opensource-experience.com/en/
#DigitalSovereignty #B1Systems #ImmutableLinux #Fedora #bootc
-
Directly after #fosdem in Brussels, #CfgMgmtCamp (Config Management Camp) will take place in #Ghent. #EU_OS just had its talk accepted. We gonna tell you more about:
EU OS use case study: #bootc based laptop fleet management with #foreman.
Most of the EU OS partners will also send their experts. Don't miss out!
-
This has been what's it's all been for...
Bots raising PRs when a container is updated. I have the ability to roll back these back if something goes wrong and the same is true of OS updates.
-
Off to orlando for IBM TechXchange. I am speaking tomorrow! So if anyone is there come by and hear me talk about RHEL as a platform for developers! Tomorrow at 11am.
I'll be talking a few features but primarily i'll be showing you live how to use podman desktop for local development and then build a RHEL image mode system from the result. Unfortunately the TSA confiscated my chickens so i won't be able to sacrifice them before my demo. So i'll be working without a net. Pray for me. ;)
#techxchange #rhel #redhat #ibm #developers #imagemode #linux #bootc
-
The recording of my third talk with Pragyan and Vitaly at All Systems Go! about UKI, composefs and remote attestation for Bootable Containers is now available: https://app.media.ccc.de/v/all-systems-go-2025-362-uki-composefs-and-remote-attestation-for-bootable-containers
#ASG2025 #AllSystemsGo #AllSystemsGo2025 #UKI #composefs #bootc #BootableContainers #RemoteAttestation
-
The recording of my second talk at All Systems Go! about how we moved Fedora CoreOS to Bootable Containers is now available: https://app.media.ccc.de/v/all-systems-go-2025-375-leveraging-bootable-oci-images-in-fedora-coreos-and-rhel-coreos
While I'm the one doing the talk, all the credit goes to Jonathan Lebon who did most of the work mentioned there.
#ASG2025 #AllSystemsGo #AllSystemsGo2025 #Fedora #CoreOS #bootc #BootableContainers
-
3/3 Thanks to the open source communities who helped and developed to the benefit of #EU_OS!
1) #foreman integration with #bootc facts export also for Fedora: https://copr.fedorainfracloud.org/coprs/rriemann/eu-os/package/bootc/
2) #bluebuild improves local deployment of OCI containers for better development https://github.com/blue-build/cli/pull/448
3) #foreman investigation of issues with OCI registry receiving large containers (ours is about 9GiB) https://projects.theforeman.org/issues/38649We got a #Matrix channel for developers at #eu-os-dev:kde.org Come over and say hi!
-
We are bringing UKI and strong boot integrity guarantees with composefs to Bootable Containers. We demonstrated our latest progress on that front at DevConf.cz 2025: https://pretalx.devconf.info/devconf-cz-2025/talk/739KGC/
-
@cgwalters we started using bootc images for Copr builders and so far everything works great.
-
Work shill. I will be running a 2 hour interactive workshop next week on #redhat #linux #imagemode AKA #bootc upstream and what forms the basis of a few really cool community projects including #bazzite / #universalblue
This is an #APAC/#ANZ friendly time-slot next Tuesday - register here : https://red.ht/3ZrFJrK
-
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 = 0The 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_IMAGENow, 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.confYou 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.initThis, 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
-
Day 2 of #hackdays2025: #EU_OS has now a new Proof-of-Concept section on the website (work in progress). The team enrolled some #bootc machines in #Foreman. The results so far were pitched to a selection board. Thanks to the great team who made this all possible! 🙏
Unfortunately, #EU_OS has not been selected to proceed to the next stage.
-
6 days until #EU_OS at Paris #HackDays: EU OS is a so-called atomic operating system that offers interruption free software updates thanks to #bootc (bootable container) technology. While people work, bootc downloads and installs unnoticeable to the user the update. After the next computer restart (trigged by the user), EU OS switches to the new version. If something breaks, the user can roll back. 1/2
#Linux #DigitalSovereignty #Microsoft #Windows #Trump #Khan #Tariffs #sysadmin #endof10
-
One thing I have from immutable (atomic) distros, and is how cumbersome is installing apps that require root permissions.
Supposedly you have to use Distrobox. Even that never worked for me. I always have to resort to `rpm-ostree` and then uninstall it so BootC can update the system. Every single time.
#Linux #Distrobox #OCI #Container #Root #Containers #BootC #RPM #PackageManager #LinuxPackageManager #LinuxDistribution #Distribution #Distros #LinuxDistro #LinuxDistros
-
Attention opensource #OS developers, this one's for you!
Got something to say about #Linux-based operating systems? #DevConf_CZ is looking for speakers to share insights on @fedora Linux, @centos Stream, RHEL, CoreOS and Silverblue, or maybe new technologies and features such as bootc, immutable systems, dnf5, Konflux, edge, and automotive.
Get your submission in: https://pretalx.devconf.info/devconf-cz-2025/cfp
#opensource #CfP #OS #Kernel #Edge #Automotive #Linux #dnf5 #RPM #bootc #Konflux
-
With Allison, I presented at FOSDEM how we can combine UKI, composefs and containers to build a fully signed boot chain. The slides and the recording are now available: https://fosdem.org/2025/schedule/event/fosdem-2025-5191--signed-sealed-and-delivered-with-ukis-and-composefs/
This is how we are planning to bring boot chain integrity to Bootable Containers.
This is a follow up on the initial work that we presented last year at @allsystemsgo: https://cfp.all-systems-go.io/all-systems-go-2024/talk/HVEZQQ/
#BootableContainers #bootc #Fedora #CoreOS #AtomicDesktpos #FedoraCoreOS #FOSDEM #FOSDEM2025
-
Fedora Linux 41 is here!
https://fedoramagazine.org/announcing-fedora-linux-41/
#Fedora #Linux #RedHat #OpenSource #GNOME #KDE #ImageMode #bootc #Containers #podman
-
#Bootc: Getting Started with #BootableContainers: https://www.youtube.com/watch?v=bf1xqjLeA9M
This is based based on #Fedora's Bootc getting started guide: https://docs.fedoraproject.org/en-US/bootc/getting-started/
See also:
* bootc: Getting started with bootable containers – by @vrothberg and Preethi Thomas: https://developers.redhat.com/articles/2024/09/24/bootc-getting-started-bootable-containers#
* Bootc: Hands on Demo: https://www.youtube.com/watch?v=fccox6sGCWA
-
Hello from Ultramarine on bootc!
(Ultramarine Atomic GNOME 41, development build) #tech #fedora #bootc #atomic #immutable #immutablelinux #ultramarine #ultramarinelinux #foss #linux -
I will definitely be taking a look at the new #ImageMode deployment method Red Hat announced yesterday during Summit. It has potential for some really cool applications and deployment cases. I'm thinking of spending some time this weekend messing around with generating @centos and @fedora images!
https://fedoramagazine.org/get-involved-with-fedora-bootable-containers/
https://developers.redhat.com/products/rhel-image-mode/overview?intcmp=7015Y000003t8u8QAA
#RedHat #RedHatSummit #RedHatEnterpriseLinux #RHEL #Containers #BootableContainers #Cloud #HybridCloid #BareMetal #BootC #CentOS #Fedora
-
🔴 📐 Today on the #VectorArtStream (Pilot) - Drawing in #Inkscape:
Chill hour drawing #Bootc icon, my mascot Bootseef - now more compatible with downscaled medium unlike the detailed version.
If you like more vector stuff, #CommunityDesignTeam, @fedora.design and @fedora projects, come check my stream next time! I enjoy explaining some intricacies, in reasonable amounts. 😅
🆕 More streams to come: https://techhub.social/@vintprox/112065524799922798
#VintproxEdutainment #Fedora #FedoraProject #RedHat #Podman #Crun #FOSS #FLOSS #FreeSoftware #OpenSource #software #Inkscape #CreativeCommons #mascot #logo #LogoDesign #VectorArt #art #design #container #containers #boots
-
Was working today on kind of an entry piece for Community Design Team: a logo and new mascot for #Bootc (special type of container).
His name is Bootseef and he's ready to fly through updates! 🚀🚀 Thanks to Madeline Peck and Design Team for the sketches, sources and color choices that inspired me. 👋 I enjoyed doing this particular mascot the most.
@fedora.design and #CommunityDesignTeam have lots of work on their plate, so I invite aspiring and designers by trade to have a looksie-look in their GitLab issues. @fedora has engineering and other teams worth their gold, making software great, as well.
#Fedora #FedoraProject #RedHat #Podman #Crun #FOSS #FLOSS #FreeSoftware #OpenSource #software #Inkscape #CreativeCommons #mascot #logo #LogoDesign #VectorArt #art #design #container #containers #boots