Awesome! So glad to see that #btrfs subvolume/compression support landed in #ImageBuilder! 🎉

https://github.com/osbuild/osbuild/pull/1312

Linux on ARM Snapdragon processor netbooks?

Easy all-devices-on-board-working install is only a matter of short time now :linux:

A work in progress: to free Samsung Galaxy Book Go's (such as NP345XLA models) to work with Linux "The Freedom OS".

There's a DEBIAN LINUX image for starters! Login with these credentials after a successful live-boot:

User= linux
Pass= changeme

The touchpad won't work yet (nor the WiFi). Are you a dev? Able to help with this effort?

DL the image & burn it to a USB-stick with for example Etcher => https://github.com/hexdump0815/imagebuilder/releases/tag/230308-01

#ARM #Linux #netbook #laptop #Snapdragon #Samsung #Galaxy #GO #development #Debian #GitHub #imagebuilder #HexDump @hexdump

I wrote a blog post a while back about shipping @fedora cloud images to Oracle Cloud Infrastructure (OCI), but now there are docs for doing this with RHEL and Image Builder! 👏

#oracle #cloud #imagebuilder #rhel #redhat

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/composing_a_customized_rhel_system_image/index#proc_pushing-customized-images-to-oracle-cloud-infrastructure_creating-cloud-images-with-composer

Are you looking to build better golden images? Meet the @RHEL #ImageBuilder tool. In this blog, we take a look at the platforms available and the decisions you'll need to make to building your Red Hat Enterprise Linux servers no matter where they live! https://sprou.tt/1eqlrGOuo15

Oh! It's been a while since I commented on #RedHat #ImageBuilder / #osbuild :D Let's correct that.

It's absolute awesome how you can set an #OpenSCAP profile directly in the blueprint. It's also completely useless :) It always performs both an evaluation and remediation step, with no option to run the remediation off, or to supply a tailored profile with added or excluded tests.

I can't imagine many images being built that don't have some form of post-processing, so running remediation beforehand is either just unwanted or worse, changes things that shouldn't be changed.

Now, I do really mean that the intention is awesome. I just think there weren't too many actual users offering input :) So, this is mine - please take it as constructive criticism.

@fossrob @jorge A default RHEL RPM OSTree image would be interesting, but I feel a bit unlikely. These kinds of images have very specific deployment cases, and Red Hat would rather leave that up to the customer to decide. This is what #RHEL for #edge is.

That being said, you can take advantage of this today by creating your own OSTree images for RHEL and derivatives using #ImageBuilder! You can then host the cuts yourself or push them into something like #Foreman to do it for you.

... aaaand conclusion:

1) Copy contents of the #redhat 8.7 DVD to disk
2) Remove dbxtool from BaseOS/repodata xml files.
3) Recalculate sha256 hashes in repomd

uh oh, turns out shim-x64 really wants dbxtool and at this point fwupd is for some reason excluded. There might be a better solution but I'm quite tired with this problem and so:

4) Remove dbxtool as requirement from shim-x64 (since we know fwupd is going to get us the binaries anyway)
5) Recalculate sha256 sums again

Done. I can now build images.

There's a Truman Show-esque suspicion in the team that we are the only ones in the world using Red Hat #Imagebuilder, looking at all the weird issues we constantly run into ... ;)

I'm sure you've been eagerly awaiting the next #redhat #imagebuilder / #osbuild story :D

$ composer-cli blueprints depsolve <name>

No issues.

$ composer-cli compose start <name> <image>

ERROR! DepsolveError:
...
- package fwupd obsoletes dbxtool
- conflicting requests

Yes. We all know fwupd has replaced dbxtool. Now please let me build?

(I have not found a solution to this yet - recall that osbuild uses its own dnf-resolve python code. Yes I've been hacking around in it with success)

(Sort of documenting my hickups with the #redhat #imagebuilder here - it's not to be seen as just pointing out errors. I will bug report)

I'm in CET, UTC+1. When I push a blueprint into the system and then use 'composer-cli blueprints changes' the timestamps shown for when the blueprints were pushed indicates being in UTC ('Z' at the end) but they are in local time.

Screws up my "did you forget to push the latest blueprint before building" script atm ;)

Alright, next surprise with #RedHat #ImageBuilder / #osbuild :) We're on Red Hat 8.6, using the DVD as repo. When trying to install Node-JS through the blueprint we kept getting 10.24, even though 16.14 is clearly there when looking at the files. Changing 'version' just meant it couldn't find the package.

Oh. That's right. To get 16.14 we need to use 'module' with yum / dnf. Without it they will also only find 10.24. So how do we do that in the blueprint then?

You could assume that would be [[modules]] - but you'd be wrong. Modules and Packages work exactly the same (as documented).

The solution is ... [[groups]] :)

[[groups]]
name = "nodejs:16"

Quote from wldr-client github:

"groups is a TOML list, so each group needs to be listed separately, like packages but with no version number."

If you say so ;) The above solution is verified working.

well well well

With no other changes made to the blueprint, building a qcow2 instead of vmdk and then directly converting the qcow2 to vmdk worked.

So at this moment I would wager that there's an issue in Red Hat 8.6 osbuild / image builder when it comes to generating vmdk type filesystems.

#redhat #ImageBuilder #osbuild

I'm sure it's #RedHat #ImageBuilder that's awesome and it's me that's confused but omg it does really feel like it's the other way around ...

Cannot mount sysroot you say? Bad superblock? Yeah well ... can't really write anything else in those [[customizations.filesystem]] now can I :/

It is easier than ever to spin up new #RHEL 9 virtual machines with #ImageBuilder. Its even better on the command line! Check out our #selfpaced lab for creating Red Hat Enterprise #Linux #VMs with composer-cli https://lab.redhat.com/tracks/imagebuilder-cli

Would you like an easier way to manage your templates and gold images? Well, it is easier than ever with #RHEL #ImageBuilder. Go check out our @RedHatSummit@twitter.com session with @itguyeric@twitter.com to learn more! https://events.experiences.redhat.com/widget/redhat/sum22/SessionCatalog22/session/1641398669945001iy8u

Have you wanted to give the new hosted #ImageBuilder a try but need some help getting started? You got you covered! Go check out our latest blog on how to get your standardized #RHEL images deployed to your #cloud provider of choice: https://buff.ly/3A68LiJ

Did you know that #ImageBuilder is a great way to deploy golden images in your environment? Now, it is also included as a service within #RedHatInsights! Go check out the #beta announcement and give it a try! Let us know how it goes. https://buff.ly/33yDQzq