FIt builds successfully in my image using this method, but I wonder how much is it broken
he disables selinux after all
he disables selinux after all
KI'm thinking closed won't fix
Fwell, the system booted without errors in VM
Don't have sealert or setroubleshooter to analyze if there are some SELinux errors
Don't have sealert or setroubleshooter to analyze if there are some SELinux errors
FBut I rebased from the existing install, didn't use the ISO method
AHe's fixing it
AAfter all he was using cosmic the OCI way
FJust testing install of Steam RPM:
rpm-ostreednf5 handle it the same way, 183 packages to install & they both install it successfullyFat least how it looks like in logs
JJIT HAS BEGUN
NI thought we were done Jorge...
Jwe are done
Jonly maintenance remains
Ntrue true true
TFmaintenance is 80% of the work according to some researches
Nsomeone probably has archived an even earlier version of this.
RGitHub's pulled the plug again
R100% of their services offline
RYou gotta respect the tactic. Their GHA SLA for enterprise customers is based on number of workflows that fail.
Workflows can't fail if you can't invoke them through commits or the API to begin with
And you can't even see their SLA right now
https://github.com/customer-terms
Workflows can't fail if you can't invoke them through commits or the API to begin with
And you can't even see their SLA right now
https://github.com/customer-terms
RThat latest Cosmic issue... 
Users who do not want to use the base Flatpaks can do so by simply basing a custom image off Cosmic. They do not inherit the ISO from us.
Also could have explained what the real issue was.
Users who do not want to use the base Flatpaks can do so by simply basing a custom image off Cosmic. They do not inherit the ISO from us.
Also could have explained what the real issue was.
Jsorry just wasn't in the mood for the lip
RAll good. Just another instance of you can't please everyone.
Jit's always the most opinionated experts talking down to everyone else that get their ass kicked by a dockerfile lol
JHeliumOS is an atomic desktop operating system for your devices.
Jthis is that one project doing centos builds from the alma bootc image, super cool stuff
RYeah. Think they are going full Bootc. I see the maintainer in the bootc matrix a lot
Jahhh, to start over fresh ...
J
JJsomeone might wanna check that out
RBefore rechunk, I was doubting the usefulness of bundling Flatpaks into the OCIs. Increases downloads for not much benefits.
Now we have rechunk, it could be a good thing to do, and would allow the switch to Bootc Image Builder ISOs sooner
Now we have rechunk, it could be a good thing to do, and would allow the switch to Bootc Image Builder ISOs sooner
Jnod
JThis is so dope
Jyeah maybe they'd help us enable centos builds lol
NThis looks really interesting.
NI see the flatpak thing is being done in a bootc image, but does it inherently rely on bootc though?
II'm actually the dev of that project
Iflatpak-readonlyroot reads toml config to configure a custom Flatpak installation, it's not specific to bootc. The name reflects the intended use case rather than technical limitations
IWhat do you have in mind?
NVery nice! Do you know if the flatpaks that get installed resolve all the dependencies during installation?
IThanks 
Yes, all dependencies are resolved
Yes, all dependencies are resolvedIThe main downside of this approach is the increased filesize. e.g. platform dependencies are not shared between the flatpak-readonlyroot installation and the typical flatpak installations
Noh, so they only update on image build?
Ncould be nice for some stuff I suppose.
IYes, the flatpaks are completely managed by the mechanism that delivers /usr instead of flatpak's package management
NI could seeing this being useful specifically for like the gnome apps and such.
Nstuff you typically wouldn't want a user to uninstall.
IExactly, I'm currently using it to deliver bootc-gtk
Ndefinitely gonna load your project up in a VM. Very interested to see what bootc-gtk looks like.
