Would a ublue EL10 image be CentOS Stream based?
Would a ublue EL10 image be CentOS Stream based?
IWhat you have in https://github.com/ublue-os/main-bootc/tree/initial-bootc-desktop-builds is exactly what I had in mind
GitHub
OCI base images of Fedora bootc with batteries included - GitHub - ublue-os/main-bootc at initial-bootc-desktop-builds
RYeah, 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.
JI 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.
R@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 
J100% don't even PR just go go go. 
RCould I have admin? I'd like to change a few repo settings
Jlike if we crib off of one of your images in order to get the rest of the stuff in place then that sounds smart to me.
Jcheck your inbox.
RThanks!
NWoooooo
BGOOO
RAnyone happen to be familiar with this error in systemd-remount-fs?
Wondering if it has anything to do with composefs in the bootc images
Wondering if it has anything to do with composefs in the bootc images
RIf I ignore that error, and manually create the gdm group, I get a desktop!
Well, the login screen. The desktop isn't loading
Well, the login screen. The desktop isn't loading
IOk, so 5 years of ublue lts? Since ublue distributes end-user images, I don't think the ability to switch to a different EL clone base will matter. The main distinction is between EL-next and EL
Isystemd works with bootc, feel free to
systemctl enable gdmIThoughts on the relationship between HeliumOS and ublue lts?
RIt's enabled by default. The primary issue is it fails to start due to gdm group not being present for some reason
IStrange. Do you have your changes pushed to your branch?
RAll changes are in the
mainHave you tried the "Fedora Workstation" group instead of gnome-desktop?
II encountered problems with NetworkManager until I installed the Workstation group
JIf I don't have to make bluefin:lts because heliumOS already exists then that would be fine with me too lol
Jlike if you want to stake the claim for an end user consumable EL atomic images I don't think you'll have much competition, heh.
Jbut if you want to bring EL expertise to the team and do it all together, also always open to doing everything as a group heh.
II will continue improving HeliumOS, but I would like to collaborate more with you and the rest of ublue.
Jalways down for that! Has anyone from centos been checking out your stuff? I'd like to get this on shaun mccance's radar if you don't mind
IJoseph Gayoso brought it up in a CentOS Stream Matrix channel, so Shaun is aware
Jah ok, perfect.
II've been most active in https://matrix.to/#/#bootc:fedoraproject.org, which some here may want to join
You're invited to talk on Matrix. If you don't already have a client this link will help you pick one, and join the conversation. If you already have one, this link will help you join the conversation
JJGitHub
This PR contains the following changes:
Add pytest-based unit tests
Add Github Actions CI for unit tests
I can squash before merging :)
Closes #72
Add pytest-based unit tests
Add Github Actions CI for unit tests
I can squash before merging :)
Closes #72
JNICE!
J@imbev a longer support desktop from the Fedora world would be crazy to see. Would be interested to see what the balance looks like between new packages and the stability from staying on something old.
JShame that it didn't stay on CentOS Stream because it would have been awesome for those guys to have a downstream example that they would like to play with, but Alma's great too. And Alma is a downstream as well.
JOn the topic of bootc, I reached out this week to help them start figuring our how they want to market and position bootc and the bootc images. We'll see where they land but it's exciting. Lots of openness to the idea of bootc being an invitation for the community to build something with it.
ICentOS Stream and AlmaLinux are similar enough that I think it will be useful
Ibootc is much more approachable for downstream projects
Jwhich i love so much
JWhat I would like to see is Fedora pick up more of the cloud native methodology that uBlue has if they don't already. But I know @Noel is looking at how that can work.
JMaybe it would be valuable to point folks from the atomic downstream community into the Fedora Atomic Desktops SIG specifically. Besides getting bootc over the line, I imagine that SIG is the next thing that is the most consequential for all of the atomic desktop downstreams. And I think Timothee would be grateful for the help.
GI'll take a look!
GI also am figuring we could use some integration testing as well, like loading up a
ublue-os/main container, installing and running ublue-update on it. Making sure the RPM installs, ublue-update works, and the systemd service functionsJ@Kyle Gospo does merging a change in ublue-os/packages auto kick off a COPR or do I need to press the button?
JI hit refresh a few times in the copr view so I'm assuming I have to hit the button
Kneed to press button
Jdone, neat.
Jmaybe someday
Gthe COPR build action uses this IIRC
