Skip to content

feat: use bootc for install - #93

Draft
renner0e wants to merge 4 commits into
mainfrom
bootc
Draft

feat: use bootc for install#93
renner0e wants to merge 4 commits into
mainfrom
bootc

Conversation

@renner0e

@renner0e renner0e commented Sep 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

See: #91

This is currently broken! We need to find out why

@codacy-production

codacy-production Bot commented Sep 12, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@renner0e

This comment was marked as outdated.

Sign in to view
@renner0e

This comment was marked as outdated.

Sign in to view
@renner0e
renner0e force-pushed the bootc branch 2 times, most recently from b0fcbdd to dbce621 Compare September 13, 2026 16:29
@renner0e

This comment was marked as outdated.

Sign in to view
@renner0e

This comment was marked as outdated.

Sign in to view
@renner0e renner0e mentioned this pull request Oct 3, 2026
Merged
renner0e added a commit to ublue-os/aurora that referenced this pull request Oct 3, 2026
@renner0e
feat(bootc): add enforce-container-sigpolicy for install (#2968)
cfc55e1 
This is a requirement for using bootc with Anaconda or else we don't
enforce signed images for subsequent updates.

In the past we have used bootc switch --mutate-in-place (in combination
with ostree-container which is what we are currently using for the
installation media), but this no longer works with bootc for whatever
reason.

This doesn't seem to matter for local builds, so this is fine to just
add here on the image.

xref: get-aurora-dev/iso#93
@renner0e
renner0e force-pushed the bootc branch 2 times, most recently from 0e4544d to b083a52 Compare October 5, 2026 06:43
@renner0e

renner0e commented Oct 5, 2026 •
edited
Loading

Copy link
Copy Markdown
Member Author

on f44 the installation fails if there is no network (after a couple minutes into running bootc install)
image

this just works fine on f45

@renner0e

This comment was marked as outdated.

Sign in to view
@renner0e

renner0e commented Oct 5, 2026

Copy link
Copy Markdown
Member Author

and the deployment path is different compared to my host system

ls /sysroot/ostree/deploy/
default

my system says fedora

seems to be

inffy
inffy reviewed Oct 5, 2026
View reviewed changes
Comment thread iso_files/configure_iso_anaconda.sh Outdated
@renner0e

renner0e commented Oct 6, 2026

Copy link
Copy Markdown
Member Author

on f44 the installation fails if there is no network (after a couple minutes into running bootc install) image

this just works fine on f45

So we either figure out what's going on with F44 regarding the offline install (if it's even our fault?) OR we make this an if and only do this for fedora 45/testing for the time being

@inffy

inffy commented Oct 12, 2026

Copy link
Copy Markdown
Member

on f44 the installation fails if there is no network (after a couple minutes into running bootc install) image
this just works fine on f45

So we either figure out what's going on with F44 regarding the offline install (if it's even our fault?) OR we make this an if and only do this for fedora 45/testing for the time being

Think at this point there is no reason to spend time on f44. We have a working ISO for it and f45 is so close.

@renner0e

renner0e commented Oct 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Member Author

Think at this point there is no reason to spend time on f44. We have a working ISO for it and f45 is so close.

Thing is that if we have to delay f45 for stable longer than the coreos delay for any reason then we can't really ship fixed f44 ISOs if we need to, we could make this a conditional for the time being and then remove it in a couple weeks

@inffy

inffy commented Oct 13, 2026

Copy link
Copy Markdown
Member

Think at this point there is no reason to spend time on f44. We have a working ISO for it and f45 is so close.

Thing is that if we have to delay f45 for stable longer than the coreos delay for any reason then we can't really ship fixed f44 ISOs if we need to, we could make this a conditional for the time being and then remove it in a couple weeks

That is probably the way to do it if we want it now. Or we do it after f45 stable goes out, but i guess we would want to do testing ISOs with it for the time being

@codacy-production

codacy-production Bot commented Oct 18, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@inffy

inffy commented Oct 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

stable (from artifacts) installed correctly.

didnt have time to test the testing iso yet

@inffy

inffy commented Oct 19, 2026

Copy link
Copy Markdown
Member

testing ISO installs but looks like flatpaks are not installed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@inffy inffy inffy left review comments
@NiHaiden NiHaiden Awaiting requested review from NiHaiden NiHaiden will be requested when the pull request is marked ready for review NiHaiden is a code owner
@ledif ledif Awaiting requested review from ledif ledif will be requested when the pull request is marked ready for review ledif is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@renner0e @inffy