Skip to main content

Making Our Own Fate: Dakota Alpha 2

· 13 min read
Jorge O. Castro
Director of Dinosaurs

The Final Shape is here...

RELEASE SOUNDTRACK TO HUNT BYBluefin and the Lost Tribe of Contributors

Ok look we made another Bluefin. I know what you're thinking (especially you McPhail!). We got rid of Bluefin GTS and now the team decided to make another one. How many of these things are there, it's like a string of Jurassic Park sequels. First let's level set. The product is Bluefin. That's the default Fedora one.

Dakota Alpha 2 desktop screenshot

Your favorite murder chicken is safe. We don't expect normal people to know what Dakota is anymore than we expect them to know what a Koenigsegg is. I can't even pronounce that name! We remain a project designed for cloud native practicioners, so we offer the very best tech the desktop has to offer. And there's good tech in BuildStream and GNOME OS, there's a compelling set of options here. This one just goes all in. I would not call yesterday's Fedora Hummingbird announcement a coincidence.

And now for the mysterious new raptor who keeps making waves:

Bluefin Dakota

latest-20260512May 12, 2026
Kernel6.19.14Gnome50.1Mesa26.0.5Podman5.8.2Nvidia595.71.05systemd260.1pipewire1.6.1flatpak1.16.6

Dakota is our newest "distroless" raptor. It's built from source and directly published as a bootc image, no traditional package manager involved at all.

Wait, this is just Gentoo.

Chris Aniszczyk, CTO Linux Foundation and former Gentoo contributor

Dakota features a more aggressive push away from legacy technologies, pure image mode only. Just the best desktop we can ship, direct from GNOME and Freedesktop SDK right to you. We remove the concept of "the Linux distribution" being a platform and the top primitive, the Freedesktop SDK libraries and Flathub are our platform. No compromises. Dakotaraptor is daily driveable and has quickly exceeded all expectations.

  • GNOME 50, Linux 6.19.x, Mesa 26.x, and Freedesktop SDK 25.08.11 libraries
  • systemd-boot, UKIs, UEFI only, compiled for the x86-64-v3 architecture level
  • Oxidized coreutils - same sudo-rs and uutils setup as Ubuntu - thanks to Canonical for funding this important work
  • Mostly feature complete, it's a full Bluefin
  • Custom Command Menu — Dakota features a newly refined menu. We hope to bring this menu to other Bluefins over time.
  • Ghostty as the default terminal

Since Dakota is brand new there's no users to transition when we switch something. We are switching to Ghostty as the default terminal. This has always been a fan favorite so we're starting with it fresh here.

Last I talked to Christian Hergert we discussed having ptyxis just use a libghostty backend. This is not only totally possible but would be the ideal situation! Someone please make this.

Changes since Alpha 1

Thanks everyone who helped test, you've done a great job!

  • LUKS encryption works on install
  • Full Nvidia Image
  • Efficient layering - this image uses the upstream chunkah tool for more efficient downloads. We expect efficient delta downloads to land sometime this summer, but the infrastructure is in place now
  • Linux 7.x kernel will land once some of the bootc issues with 7.x are resolved
  • Beta target: Probably a month or so; GA target: Fall 2026
  • Want to help? GNOME OS upstream is always looking for help: os.gnome.org

Gotchas

And the big one. We cannot guarantee that this installation will be the final layout. GNOME OS is transitioning to systemd-homed eventually. That will mean either a manual transition or reinstallation. As such we likely will not go GA until this transition completes. We expect a lazy summer beta.

What now? It has been an absolute pleasure working with BuildStream over the past few weeks. The team has committed to the hardware necessary to make builds faster and the local development experience has been the best we've ever had. It has become clear and obvious to me that the combination of BuildStream and bootc brings a level of automation and developer experience that will be tough to beat.

Here's the hot take: If you look at all three raptors, all else being equal, the best development experience and best infrastructure always wins in this space. We have over a decade of cloud native industry experience to prove it, Kubernetes runs the world for a reason. This workflow is now in the Linux desktop space. I firmly believe that buildstream/bootc combined with our gitops approach will deliver a fantastic product.

Thanks to Brian Ketelsen and James Reilly for the Tuna installer. Yes they called it the Tuna installer. lol.

Thanks to Jordan Petridis, Valentin David, Adrian Vovk, Felicitas Pojtinger, and the GNOME OS team for their expertise and advisory roles - we couldn't do this without you!

Bluefin's Download Diet: Introducing Chunkah

Yes, they called the upstream rechunker "Chunkah". A rechunker is a thing we use to take an image and reslice it into more chunks. ghcr.io/projectbluefin/dakota is sliced into 120 layers instead of one big unresumable download for updates. It also takes content of the image into account. The idea being if you have components that update often, they would be group together in layers, and things that don't get updated often are group together.

That means if your computer doesn't need that layer for that update, it doesn't get downloaded. Additionally partial zstd:chunked pulls will complement the layering. This will mean that your computer will also only download the parts of the layers it needs. When combined this finally brings efficient downloads to the bootc ecosystem. Initial findings are looking good.

These alpha images are rechunked by Chunkah, but unified storage does not work on the composefs backend to bootc yet so it's not done.

Why tho? A Call to Action

After all that praise of an alpha product of all things, some may misconstrue this as abandonment of the other Bluefins or a lack of focus. Now let's talk about how we got here.

Disclaimer

This section is my opinion and does not reflect the views of the team, but is instead a reflection of my 20+ year journey working in Linux.

-- jorge

The Shoulders of Giants

Bluefin's mission is sustainaiblity, that means people. Bluefin LTS is there so we have a reason to bring people like Carl George and Shaun McCance into our ecosystem. Without Bluefin LTS Red Hat would not have as much of a financial incentive to help us out. We drive bootc forward, they invest in the software and sell it as part of their product. It's the Circle of Life, but with Linux. Red Hat did afterall, give us millions of dollars of engineering for free.

Same thing with Fedora, it's our line to that center of gravity. And we have a new approach with Fedora Hummingbird, attracting more people. It's not about the software, it's about the ecosystems we make along the way. Sounds like the kind of tripe the Linux Foundation loves to peddle! Dakotaraptor has one foot in the bootc world and one in the UAPI world.

Speeeeed

We will participate in both of those large ecosystems; that brings in the largest group of talent. Projects live and die based on the contributors that show up. We will always endevaour to work the best people at the cutting edge of Linux. We're ops people, mastery of all Linux is a requirement.

The CNCF Community via bootc, composefs, podman, and oras. The UAPI community bringing in the Linux userspace. Sounds great, let's go. Someone from Amutable please save me a shirt!

The Race to Sustainability

Colin Walters describes communities like this as "Centers of Gravity" - and we're all in one gigantic galaxy, everyone pulling and pushing around different ecosystems. All made possible by open source tools, amazing.

The state of Dakota Alpha 2 is impressive considering how few people it took to make it. For us our job is to make Bluefin as thin of a config layer as we can, our opinions are mostly in userspace anyway. It should be noted that this way is always cheapest. It is always cheaper to fix things upstream closer to the source. It's called "shifting left", yes there's a term for it lol. Welcome to cloud native.

It's here

There are those that will say that GNOME OS and KDE Linux make no sense, that's what distributions are supposed to do. I push back against that. 4% marketshare in 30 years is not a success story. And the ones that are growing are designed to be used as reliable clients and not package manglers.

Timothée Ravier once said, people don't want distributions they want experiences. And these operating systems will prove it. No one will ever give you a better KDE experience than KDE. That wasn't true in the past because distributing software over the internet was hard. Now not only is it much easier, these organizations can start greenfield with the state of the art rather than trying to adapt old techniques to the new world.

Best infrastructure wins. Fastest and cheapest development wins.

If you're into GNOME work on GNOME OS, if you're on KDE work on KDE Linux. If you like Fedora work on that. Make a friend, donate to an app developer.

Prove it, nerd

I will be discussing this in my talk at the Linux Application Summit: Making our own Fate: Why GNOME and KDE need operating systems - be there!

This is of course, all from our point of view.

GNOME OS would prefer we ship a DDI image. And some would prefer we don't exist at all and just sit as a systemd-sysext in GNOME OS. Sure, someone make one, we have buildstream, would you like fries with that? And with so many RPM-based people in the bootc world I am sure there are people who prefer that Bluefin just focus on being a Fedora with batteries included and nothing else.

But we are a forcing function - the dinosaurs are there to remind us that only the best survive the harshest ecosystems. This is especially true in the resourced starved Linux desktop ecosystem. We will continue to push. Some software is not going to make it. See you in the trenches, thanks!

It really is just a conspiracy

We built Universal Blue. Aurora, Bazzite, and Bluefin, as a team.

Then opportunites opened up for our contributors to work for organizations at the forefront of Linux. The Linux Foundation, Microsoft, Chainguard, Red Hat, and others. Driven to build around open standards but leaving room for commercial entitities to exist and thrive. And that's just the core team, as you can see from our contributor lists, the cloud native ecosystem is a significant center of gravity in open source.

You have proven that enthusiasts matter and can shape the future of the desktop. Level up your skills and organizations looking for open source talent will take you seriously, and in today's brutally competitive job marketplace, expertise in open source matters.

There's no right way to Linux, but there are certainly wrong ways to Linux. If you're new to Linux, welcome. We are your starter dungeon. We're your sysadmin team, nice to meet you, we've got your back. Greatness awaits. And also pain. Mostly pain.

Merch

Celebrate the release of a new top predator with our stylish "Dakotaraptor Forever" shirt.

Check out the rest on store.projectbluefin.io →

Download

The Resonant Assembly

One last group of people to thank. These community members participated in GitHub Discussions over the last six months. Asking questions, sharing tips, helping newcomers, and keeping the conversation going is just as valuable as code. Thank you for your help, it's important!

The Resonant Assembly

Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...

Filing Issues

Discussion Thread