Bluefin and Aurora 3.4.0

Bluefin and Aurora
,
1

kate
kate1296Ă—1296 260 KB

Another boring one, most of this stuff is overly nerdy.

There is one major change for those of you who have opted into bluefin:latest. P5 has turned on the rechuncker. Bazzite has been using this for a while so this is more catch up for us. This reorganizes the layers in the container image to be more efficient.

  • Enjoy ~1GB in space savings
  • The download layers will now be smaller and evened out. (No more huge 2GB layer tacked on at the end of you -dx users)
  • Upgrades in general should be a bit faster
  • The initial download will be quite large, 3GB since we’re basically reorganizing the image. Subsequent daily downloads will be much smaller moving forward.

If you’re using a bluefin:gts (default) or bluefin:stable build we’ll turn this on for the builds next week after getting in some runs with the dailies.

Note that this is only a partial solution, zstd:chunked images will arrive later, you can track that work here: Move to zstd:chunked container images (#9) · Issues · fedora / bootc / Issue Tracker · GitLab

3.4.0 (2024-09-27)

Features

Bug Fixes

14 Likes
2

Thank you and the reset of the Ublue team for all your work Bluefin and Aurora!

4 Likes
3

do u have the transparent versions to those new dino’s?

been struggling to cut around the details using GIMP, lol, ran out of wind through frustration, lol

image
image1544Ă—1056 102 KB

4

Here’s a read only link to the original artwork:

https://drive.google.com/drive/folders/1dZXjPFy1KgMtElUhTtcMKpSIeaLbSJwr?usp=sharing

1 Like
5

image
image1131Ă—919 168 KB

just nutted it out on gimp

6

image
image1920Ă—1080 179 KB

for now, konsole is the way tbh

1 Like
7

Hi, quick question - I’m a super happy user of ublue-os/kinote-main:latest but the total size of the layers (on average 1GB for “chunk layers” and 1.8GB for “custom layers” given a weekly cadence) and the associated download time in excess of 30 minutes are somewhat of a pain. The chunks are also quite uneven (varying between 20MB and 400MB for regular chunks and over 1GB for custom layers) although not sure if it is important.

(why base image and not Aurora - originally I switched from official Kinoite as I was interested in drivers - mainly hardware acceleration - and performance/battery but not in the user-facing tooling added on top of Kinoite, I really like the OS clean; my intel laptop seems to be well supported - it’s not clear I would benefit from akmods included in Aurora)

My question here is whether the rechunker mentioned in the announcement would help reduce the size of the base image as well and whether this is something you are planning for the base images as well. Sorry if this is a stupid question - I see the warnings that base images are not recommended for direct desktop consumption but none of the documentation spell out exactly why for the n00bs like me.

(to be fair the download times depend heavily on day of week and time of day so definitely driven by CDN not I’m being routed to, the size doesn’t help though)

8

Rechunker redoes the entire image so it makes sense to do it at the last step, so you’d want to add rechunker to a custom image of kinoite-main. It does take a significant amount of time though, and doing that to the main images is the equivalent of prepping the dough, packaging it, then handing it the next person who then has to unpackage it just to put it into the oven. It’s better to do that after the pizza is cooked. :smile:

There are no stupid questions! The main images are there for people to make their own custom images, we don’t consider them to be final products. We use them to make Aurora, Bazzite, and Bluefin and then for people to make their own if they want.