I'd like to do things like fix the broken ISOs and stuff before we deep dive into this stuff though
I'd like to do things like fix the broken ISOs and stuff before we deep dive into this stuff though
Abusiness speech mode
AYeah I heard the ISOs don't retry during download failures for example. :S
AIt's just a kickstart script so I dunno how we could solve that. Checking exit code and retrying a few times?
JGitHub
What happened? When using the iso to install ublue a rpm-ostree-backend error occurs mentioning invalid reference for OCI container ostree format. Relevant log output $ plasma-discover rpm-ostree-b...
Jthe installer issue is Anaconda, not us
AThat's strange,
docker://?Jhopefully all the info is in the ticket
Jcan you toss the results of your findings in the issue if you don't mind?
PSure yeah
AI see, so the installer is rewriting the URL to
docker://. But that doesn't seem to be the actual issue anyway, they quoted docs which say it's equivalent.
Bdo you need something from me on this? the main thing I know is missing was when I discovered this:
https://github.com/ublue-os/isogenerator/issues/64
I don't know if we want that sorted before announce or no
https://github.com/ublue-os/isogenerator/issues/64
I don't know if we want that sorted before announce or no
JWhere do we put the keys in this repo?
Jlike is it just inline replacing the files?
JGitHub
An action to generate custom ISOs of OCI images. Contribute to ublue-os/isogenerator development by creating an account on GitHub.
Bno, not a replace... we need both, and to import both, I can handle it, just wondering if we want it wrapped up before announce
PTo my understanding: the actual issue is ostree supports both
ostree-unverified-image:registry: and ostree-unverified-image:docker://, but discover only currently expects ostree-unverified-registry:, not anything else, so ostree-unverified-image:registry: or ostree-unverified-image:docker:// which should both be equivalent cause it to not work properly.
Bback reading what does preso mean?
Jpresentation
Jyeah willing to bet this is just the discover rpm-ostree work being unfinished
Jbecause a) that's the only thing that makes sense
Jand b) we know that it's in progress, heh.
J
Jbut hasn't been reported yet
AThis makes total sense. Nice find.
POnce I finish writing things up on 132, I can go ahead and file the issue on the discover side if you want
Jthat'd be amazing. It's our most popular image by far so we should help where we can.
Bwatching this! awesome! Colin has created starter OCI for CentOS to use with bootc AND bootc has opinionated LUKS support ... it can enable tpm2-luks out of the box! no need for my custom scripts anymore i guess
Jok so am I uploading a new key to this isogenerator dir?
Jwhat should I call it, I'm assuming I put it alongside the existing key?
Bno
Bi'm making a PR now
Bwe also need to modify script
B@j0rge so the gotcha on adding the second key the ISO
it'll be importing 2 keys, so we need to update docs to say when the user imports keys in the ugly UEFI MOK utility, they'll have to approve importing 2 keys
it'll be importing 2 keys, so we need to update docs to say when the user imports keys in the ugly UEFI MOK utility, they'll have to approve importing 2 keys
Bi should probably wipe my keys and test this
Junderstood, standing by
Bwho knew this "move a key to org secrets" was such a PITA 
Jplay nvidia games, win nvidia prizes
Bok, i just scrounged parts and built an nvidia machine... lets see if it boots
B@j0rge ok, what do you think about this PR goes into iso generator and we try to rig up pre-release build somehow, can we do that?
Jez
Bthen i can test that on my franken-vidia box
BJwe're set to normal release not prerelease ootb tho
Jdone with the perms
Bthanks guess we missed that one
Jyeah we need to move to groups, etc.
Clol
Bi know it' s not pretty but i think this is all we need https://github.com/ublue-os/isogenerator/pull/65/files
Bi really want to just run this locally to generate an ISO before we even merge that
Junderstood
