What I'm seeing as a difference is that ublue is using `ostree container commit` for each layer of t

What I'm seeing as a difference is that ublue is using

ostree container commit

ostree container commit

ostree container commit

ostree container commit for each layer of the image, while bootc-derived images are able to use the Container's own layers without that step.

Iimbev What I'm seeing as a difference is that ublue is using `ostree container commit`...

Kyle Gospo•8/15/24, 5:07 PM

not required, that was a recent change

Kyle Gospo•8/15/24, 5:07 PM

that just does some cleanup prior to layer generation, such as wiping out temporary files

antheas•8/15/24, 5:08 PM

ostree container commit cleaned var essentially

Jj0rge can someone paste in the architecture diagram for imbev? sorry in a call

AfterStory•8/15/24, 5:08 PM

https://universal-blue.discourse.group/docs?topic=1523

Universal Blue

Architecture Diagram

Hadn’t heard of that specifically, but had herd of similar projects. Didn’t use one, because I didn’t have time to learn one, and I think the results would be less aesthetically pleasing.

antheas•8/15/24, 5:08 PM

if you use rechunk it will also clean var so you dont need it

antheas•8/15/24, 5:09 PM

i should try to build kinoite using "from fedora"

antheas•8/15/24, 5:09 PM

that would be a flex

antheas•8/15/24, 5:09 PM

future plans

imbevOP•8/15/24, 5:17 PM

I'm thinking of the following:

Refactor ublue-os/main to FROM quay.io/fedora/fedora-bootc:VERFROM quay.io/fedora/fedora-bootc:VER, replace rpm-ostree calls with standard dnf calls. There're a few hacks that need to be done with bootc, but it can otherwise be treated like mutable fedora most of the time within the Containerfile
Refactor downstream images in the same way
The rest might be able to be reused as is

imbevOP•8/15/24, 5:18 PM

Would a branch or strangler strategy be preferred?

Iimbev I'm thinking of the following: - Refactor ublue-os/main to `FROM quay.io/fedora...

Robert•8/15/24, 5:18 PM

We could, but then we have the added burden of managing package lists for Gnome, KDE etc, which we don't currently do
Right now, we just FROM quay.io/fedora-ostree-desktops/{silverblue|kinoite|something}:VERFROM quay.io/fedora-ostree-desktops/{silverblue|kinoite|something}:VER and it's all managed by others

imbevOP•8/15/24, 5:20 PM

Is there a significant difference between the atomic desktops and the mutable variants using the corresponding package group other than the immutability?

Iimbev Is there a significant difference between the atomic desktops and the mutable va...

Noel•8/15/24, 5:21 PM

Timothee would be a good one to ask on that. He is in Matrix in the Atomic desktops channel.

Noel•8/15/24, 5:21 PM

I don't see him too often in here.

Iimbev I'm thinking of the following: - Refactor ublue-os/main to `FROM quay.io/fedora...

j0rge•8/15/24, 5:23 PM

hah yeah this is what we're supposed to be doing, we got some repos we cloned as main-bootc, hwe-bootc, etc but I don't think we're using them

j0rge•8/15/24, 5:24 PM

I'm not sure if we need to have a ton of new repos, we could just opportunanistically snag swap the common ones like gnome/kde, as those come online.

Jj0rge I'm not sure if we need to have a ton of new repos, we could just opportunanisti...

imbevOP•8/15/24, 5:26 PM

It'd be simple to switch the base image and remove a dnf groupinstalldnf groupinstall once upstream Fedora produces them

j0rge•8/15/24, 5:27 PM

how's the tool song go? save us from our wanton slumber?

Zoid•8/15/24, 5:28 PM

i was wondering when we would get to doing this. Very interesting. what does groupinstallgroupinstall do? I dont think ive ever seen that

ZZoid i was wondering when we would get to doing this. Very interesting. what does `gr...

Noel•8/15/24, 5:28 PM

it's a DNF command. There are groups of packages you can install and allows you to install all the ones you need. An example would be like the Gnome DE or KDE DE.

Iimbev I'm thinking of the following: - Refactor ublue-os/main to `FROM quay.io/fedora...

antheas•8/15/24, 5:29 PM

if you do that you will get an invalid selinux policy and invalid permissions on your directory tree

antheas•8/15/24, 5:29 PM

and it will not boot

Aantheas if you do that you will get an invalid selinux policy and invalid permissions on...

imbevOP•8/15/24, 5:29 PM

I haven't encountered that with bootc, but that might be relevant to rpm-ostree -> bootc migration

antheas•8/15/24, 5:30 PM

the reason you ahvent is because youre using an image that has the DE in the commit

antheas•8/15/24, 5:30 PM

so it has correct SELinux and correct directory permissions

antheas•8/15/24, 5:30 PM

if you make the base commit smaller, such as using an image without a DE it doesn quite work

antheas•8/15/24, 5:30 PM

the guys here had this problem with cosmic too

antheas•8/15/24, 5:30 PM

they needed to use a workaround for selinux

Aantheas the reason you ahvent is because youre using an image that has the DE in the com...

imbevOP•8/15/24, 5:33 PM

I don't think that's the case, dnf list installed | grep -i gnomednf list installed | grep -i gnome has no output within the AlmaLinux bootc image

antheas•8/15/24, 5:34 PM

and does it boot?

imbevOP•8/15/24, 5:34 PM

I believe so, but I can confirm that rq

antheas•8/15/24, 5:34 PM

whats the link to almalinux

Aantheas whats the link to almalinux

imbevOP•8/15/24, 5:35 PM

That's the base image that I'm using, and that image does not contain a DE

antheas•8/15/24, 5:35 PM

can you link me?

Robert•8/15/24, 5:35 PM

https://codeberg.org/HeliumOS/bootc/src/branch/dev/9/Containerfile#L17

Codeberg.org

bootc/9/Containerfile at dev

antheas•8/15/24, 5:35 PM

foudn it

antheas•8/15/24, 5:36 PM

didnt lol

antheas•8/15/24, 5:39 PM

ok went through it, its essentially a variant of the fedora-bootc

Aantheas and does it boot?

imbevOP•8/15/24, 5:39 PM

Confirmed, it does boot

antheas•8/15/24, 5:41 PM

where is the policy for gnome?

antheas•8/15/24, 5:41 PM

selinux-policy-targeted?

Aantheas ok went through it, its essentially a variant of the fedora-bootc

imbevOP•8/15/24, 5:41 PM

Exactly, the AlmaLinux image uses the Fedora bootc config as a git submoduel

antheas•8/15/24, 5:41 PM

could be that, so it was only an issue with cosmic

antheas•8/15/24, 5:42 PM

https://packages.fedoraproject.org/pkgs/selinux-policy/selinux-policy-targeted/fedora-40-updates.html seems so

selinux-policy-targeted-40.24-1.fc40 - Fedora Packages

View selinux-policy-targeted-40.24-1.fc40 in Fedora 40. selinux-policy-targeted: SELinux targeted policy

antheas•8/15/24, 5:42 PM

so its included in the base commit

Jj0rge yeah I'd love to have centos as a tag option in the main images. Like we have :l...

imbevOP•8/15/24, 5:55 PM

Would a ublue EL10 image be CentOS Stream based?

RRobert We could, but then we have the added burden of managing package lists for Gnome,...

imbevOP•8/15/24, 5:58 PM

What you have in https://github.com/ublue-os/main-bootc/tree/initial-bootc-desktop-builds is exactly what I had in mind

GitHub

GitHub - ublue-os/main-bootc at initial-bootc-desktop-builds

OCI base images of Fedora bootc with batteries included - GitHub - ublue-os/main-bootc at initial-bootc-desktop-builds

Robert•8/15/24, 5:58 PM

Yeah, it's not as bad as I expected. rpm-ostree doesn't support those meta groups, so I thought we'd have the same issue here.

Iimbev Would a ublue EL10 image be CentOS Stream based?

j0rge•8/15/24, 6:06 PM

I would think so, just get it directly from there is what I'm thinking, and then people could swap out to alma/rocky/whatever and we don't have to choose the right or "wrong" one.

Robert•8/15/24, 6:12 PM

@j0rge Can I takeover the main-bootc repo? It's currently re-pushing the base fedora-bootc image, but I'd like to use it to start building bootc desktops

What I'm seeing as a difference is that ublue is using `ostree container commit` for each layer of t

Similar Threads

Similar Threads

Similar Threads