CoreOS and Atomic Unification #137

Open
opened 2026-09-01 14:47:25 +00:00 by nimbinatus · 13 comments
Owner

From: https://gitlab.com/fedora/bootc/base-images/-/work_items/84 and https://github.com/coreos/fedora-coreos-tracker/issues/2214

Opened a corresponding ticket over in the CoreOS issue tracker: https://github.com/coreos/fedora-coreos-tracker/issues/2214 where the CoreOS community thought this would be a good idea to pursue.
The summary of that is that I think having Fedora bootc base images and Fedora CoreOS be similar, but separate things within the Fedora ecosystem is more of a hindrance than it's worth and I'd like to propose we merge our efforts in the future.
I've been toying with the idea for a long time of bringing these two efforts together (see last few slides from my 2025 Flock talk here), but I think it's time to actually try to do it.
Assuming people think this is a good idea what I'd like to do is form a working group on the topic of bringing the the bootc and CoreOS communities and outputs together for Fedora 46. This means not only sharing meetings, trackers, tests, pipelines, but also (most importantly) outputs. Changing the output to be unified would mean all the other things I mentioned (meetings, trackers, tests, pipelines) would just happen naturally.
Intentionally left out here are any details. This is socialization of a high level shift in strategy for our community and we'll start with talking about things at a high level prior to digging into the gritty details (and oh, there will be details!!).
If people think this is the right thing to do it will be similar to the Atomic Host and Container Linux upstream efforts coming together. A lot of good engineering discussions about tradeoffs and ultimately community decisions that leave us in a better place.

Please comment here if you want to be involved.

From: https://gitlab.com/fedora/bootc/base-images/-/work_items/84 and https://github.com/coreos/fedora-coreos-tracker/issues/2214 >Opened a corresponding ticket over in the CoreOS issue tracker: https://github.com/coreos/fedora-coreos-tracker/issues/2214 where the CoreOS community thought this would be a good idea to pursue. >The summary of that is that I think having Fedora bootc base images and Fedora CoreOS be similar, but separate things within the Fedora ecosystem is more of a hindrance than it's worth and I'd like to propose we merge our efforts in the future. I've been toying with the idea for a long time of bringing these two efforts together (see last few slides from my 2025 Flock talk here), but I think it's time to actually try to do it. >Assuming people think this is a good idea what I'd like to do is form a working group on the topic of bringing the the bootc and CoreOS communities and outputs together for Fedora 46. This means not only sharing meetings, trackers, tests, pipelines, but also (most importantly) outputs. Changing the output to be unified would mean all the other things I mentioned (meetings, trackers, tests, pipelines) would just happen naturally. >Intentionally left out here are any details. This is socialization of a high level shift in strategy for our community and we'll start with talking about things at a high level prior to digging into the gritty details (and oh, there will be details!!). >If people think this is the right thing to do it will be similar to the Atomic Host and Container Linux upstream efforts coming together. A lot of good engineering discussions about tradeoffs and ultimately community decisions that leave us in a better place. Please comment here if you want to be involved.
Member

I'm in to skyrocket this 🚀

I'm in to skyrocket this 🚀
Owner

I think there's three aspects to unification:

Build side

  • monorepo for images?
  • Konflux
  • Making it easier to reproduce FCOS-like things (including Ignition) w/o the whole CoreOS assembler thing

User side

  • Merging documentation (does this become more like "start with FCOS, but if you want to deeper customization then fork"? I think that'd kind of work).
  • Except things like the stream and auto-updates concept becomes very up-front fast. These two kind of conflict in various ways.

Community

  • Discussion forums
  • Meetings
  • Issue trackers
  • git repositories (this one is related to the build side of course)
I think there's three aspects to unification: # Build side - monorepo for images? - Konflux - Making it easier to reproduce FCOS-like things (including Ignition) w/o the whole CoreOS assembler thing # User side - Merging documentation (does this become more like "start with FCOS, but if you want to deeper customization then fork"? I think that'd kind of work). - Except things like the stream and auto-updates concept becomes very up-front fast. These two kind of conflict in various ways. # Community - Discussion forums - Meetings - Issue trackers - git repositories (this one is related to the build side of course) -
Member

I think this is the natural progression and I'm excited to participate.

I think this is the natural progression and I'm excited to participate.

Makes sense.

Makes sense.

I'll be available for this as well.

I'll be available for this as well.
Member

Hey all. Working with Laura we organized a time next week to continue the conversations here (video call) at Thu, September 10, 2026 - 12:30 UTC

Details (convert to local timezone or add to your calendar) here: https://calendar.fedoraproject.org/SIGs/2026/9/10/#m11432

We'll formulate an agenda and also add links for notes/video next week.

Hey all. Working with Laura we organized a time next week to continue the conversations here (video call) at ` Thu, September 10, 2026 - 12:30 UTC` Details (convert to local timezone or add to your calendar) here: https://calendar.fedoraproject.org/SIGs/2026/9/10/#m11432 We'll formulate an agenda and also add links for notes/video next week.

Primarily looking at this from a downstream/user perspective, unification is appealing.

Happy to contribute where I can.

Primarily looking at this from a downstream/user perspective, unification is appealing. Happy to contribute where I can.
Member

I'm in !

I'm in !
Author
Owner

I've made a calendar invite, and will happily add anyone interested if I can find your email (if you've commented and I haven't been able to find an email, I'll reach out to ask for your preferences on being added or just being sent the link privately). We will also post the link to the call closer to the meeting (note this will be on Google Meet).

The call will fall under the Fedora Code of Conduct, found at https://docs.fedoraproject.org/en-US/project/code-of-conduct/

Any and all folks interested are welcome. Feel free to reach out to me (@nimbinatus in all communication channels or via email at l.santamaria@redhat.com) if you have any concerns you'd like to voice privately.

Note that this call will be recorded and transcribed by Gemini, so I'm happy to be your voice if you are uncomfortable being on the recording (so you'll be able to mute your video and audio so you do not appear). A DM on Matrix/Slack/wherever you can find me or an email will reach me (though social network pings won't as I avoid them during working hours).

I've made a calendar invite, and will happily add anyone interested if I can find your email (if you've commented and I haven't been able to find an email, I'll reach out to ask for your preferences on being added or just being sent the link privately). We will also post the link to the call closer to the meeting (note this will be on Google Meet). The call will fall under the Fedora Code of Conduct, found at https://docs.fedoraproject.org/en-US/project/code-of-conduct/ Any and all folks interested are welcome. Feel free to reach out to me (@nimbinatus in all communication channels or via email at l.santamaria@redhat.com) if you have any concerns you'd like to voice privately. Note that this call will be recorded and transcribed by Gemini, so I'm happy to be your voice if you are uncomfortable being on the recording (so you'll be able to mute your video and audio so you do not appear). A DM on Matrix/Slack/wherever you can find me or an email will reach me (though social network pings won't as I avoid them during working hours).
Member

We started to draft an agenda today: https://hackmd.io/@dustymabe/SJN7GR6dze

We started to draft an agenda today: https://hackmd.io/@dustymabe/SJN7GR6dze
Author
Owner

Please find today's call recording and all here:

Please find today's call recording and all here: - https://nimbinatus.fedorapeople.org/2026_09_10-CoreOS_Atomic_Unification-Chat.pdf - https://nimbinatus.fedorapeople.org/2026_09_10-CoreOS_Atomic_Unification-Gemini_Notes.pdf - https://nimbinatus.fedorapeople.org/2026_09_10-CoreOS_Atomic_Unification-Recording.mp4 (**Note:** I may need to delete this in the future to free up space. I will commit to hosting this for at least 1 month :) Please download it if you want it for your records!) - https://nimbinatus.fedorapeople.org/2026_09_10-CoreOS_Atomic_Unification-Slides.pdf
Author
Owner

The next call has been scheduled at the same time this week. Details at https://calendar.fedoraproject.org/SIGs/#m11440

Please let me know if you want to be added to the calendar invite like last time!

The next call has been scheduled at the same time this week. Details at https://calendar.fedoraproject.org/SIGs/#m11440 Please let me know if you want to be added to the calendar invite like last time!
Author
Owner

The notes and recording from the last call are live at https://nimbinatus.fedorapeople.org/#unification.

If you want to work on this with us, we're rescheduling the Tuesday Atomic Initiative meeting and repurposing it to discuss unification. ACTION: Please use this link to share your availability so I can try to include everyone who's interested: https://timeful.app/e/D3ddc. I'll leave that up through the end of next week (so ~25 Sept 2026). More details on meeting cadence: #138 (comment)

We will be tracking our work in https://forge.fedoraproject.org/atomic/-/projects/750

The notes and recording from the last call are live at https://nimbinatus.fedorapeople.org/#unification. If you want to work on this with us, we're rescheduling the Tuesday Atomic Initiative meeting and repurposing it to discuss unification. **ACTION: Please use this link to share your availability so I can try to include everyone who's interested: https://timeful.app/e/D3ddc.** I'll leave that up through the end of next week (so ~25 Sept 2026). More details on meeting cadence: https://forge.fedoraproject.org/atomic/tracker/issues/138#issuecomment-1357904 We will be tracking our work in https://forge.fedoraproject.org/atomic/-/projects/750
Sign in to join this conversation.
No milestone
9 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
atomic/tracker#137
No description provided.