it installs but subsequent Discover (the kde app) crashes if it's on -image
it installs but subsequent Discover (the kde app) crashes if it's on -image
Jhttps://github.com/ublue-os/main/issues/132 is what we have rn
GitHub
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...
JI only fired up the VM today but in and out with calls for a while
Amm in that case I think isogenerator is out of the woods
Jyeah I have only chosen it on boot, installed it, and I did the status
Bwhoa. WTF
AYou were able to reproduce?
Bthis is my machine... why do i have both URL patterns?
AI think this is rpm-ostree internally
Aostree-unverified-registry:quay.io/exampleos/custom:latest - this will pull from a remote registry, and no signature will be required. In practice, this is just a shorthand for ostree-unverified-image:docker://quay.io/exampleos/custom:latest.
AThose two things should be equivalent?
Byeah, so we think Discover just can't handle the "longhand" format?
ABut I'm not sure what changed to make it show the full version
AMaybe some rpm-ostree update changed the way things are displayed
PI think this is supposed to be ok
ostree-unverified-image:docker://ghcr.io/bsherman/silverblue-nvidia-custom:latest
Bit certainly works for
i've got a couple machines showing
but one still running on
rpm-ostreei've got a couple machines showing
image:docker:// style for stuff newer than 38.20230514.0but one still running on
38.20230509.0 which has a new image still showing registry:ghcr.ioPAt least digging through https://github.com/ostreedev/ostree-rs-ext/blob/main/lib/src/container/mod.rs, It looks like
ostree-unverified-image:docker:// should be equivalent to ostree-unverified-image:registry: or ostree-unverified-registry:PYeah, at least as far as direct ostree handling I think that's fine? Maybe Discover isn't handling something correctly here?
PLooks like they're doing some custom handling of things that's maybe causing the issue here https://invent.kde.org/plasma/discover/-/blob/master/libdiscover/backends/RpmOstreeBackend/OstreeFormat.cpp#L38
Jyeah I bet it's a thing in discover because both gnome-software and discover aren't really set up for this method at all
Jlike they probably won't even start work on it until the infra is starting to land, etc.
AIf we can confirm a crash or something we can file an issue to track it
Bthis is interesting, i found a machine which still had
in the background it used to the
but on reboot was still
registry: style references:in the background it used to the
image:docker:// formatbut on reboot was still
registry:J
JI'll add it to the issue
Jbut doesn't have any info
BI guess we all know it seems like at least rebasing to
registry: will fix the issue for now... but yeah, why the image reference format changes is unknownJquick intros, I'd like to introduce @w8emv, he works on equinix metal and has just donated an ARM builder for us, so thanks for that. 
Whey hey
J@marcoceppi will handle setup and stuff and then I'm guessing @akdev will want to play first.
PI wonder if the change is caused by some serialization/deserialization that's converting one into the other?
PI'd bet that could be what's happening based on https://github.com/ostreedev/ostree-rs-ext/blob/main/lib/src/container/mod.rs#L222
A@w8emv hey 
welcome
welcomeJI am unsure of fedora's plans for ARM builds for OCI containers, so if someone knows or knows how to look or who to ask that would help
Jthey are making arm builds of silverblue and folks, but not of the OCI containers
Jso maybe if they don't plan on adding those soon we do make LXQt and MATE by hand via ostree, which means we could conceptually just build those natively
Bwe could just use cgwalters' method of encapsulation for arm builds
Wthanks @akdev @j0rge for the intro. for a little background, I do our open source partner program at equinix, we support a batch of CNCF projects with the help of @jeefy , and another batch of networking, operating systems, programming languages, and some low-level stuff as well.
Wone big gap though is fedora-based stuff which is one reason I'm excited about this effort
Athat's sounds super cool! I'm a SysDE at Amazon, just burn few cycles here when I can because I love open source and containers in general
Jlol we're all connected
Ait's very nice group of people here
POh cool. I was an SDE at Amazon (part of the robotics org), up until the recent layoffs 
AOh sorry to hear, I hope you land on your feet - I'm part of AFT, not as cool
PThanks! Yeah I think I'll probably be fine, just really starting to get into looking though, took a few months off to just not worry about things and finally go see some friends across the country etc.
I was technically part of AT (despite being on the east coast), got to do a bunch of infrastructure/edge device management stuff that was a lot of fun.
I was technically part of AT (despite being on the east coast), got to do a bunch of infrastructure/edge device management stuff that was a lot of fun.
JI'm here on a transitionary "don't have a job" too, so it's a nice support group.
J@bsherman ok I understand what we need to do to make new keys, I have dad and gaming clan commitments tonight though
BHuzzah!
JI think if someone can whip up an announcement in the nvidia forum section with the link to the instructions and stuff and then we can edit/fix it up later, I have to afk for a bit
Jor hackmd up a draft
BI assume that new private key is in the org-level secrets, right? 
