@akdev huh, this just happened: https://github.com/ublue-os/main/issues/132

J

j0rgeOP•5/18/23, 12:29 PM

I can't even find a usage of

ostree-unverified-image

ostree-unverified-image

anywhere in the org (new github code search rocks btw), so I'm wondering how this can be cropping up

Jj0rge I can't even find a usage of `ostree-unverified-image` anywhere in the org (new ...

C

ChaiQi•5/18/23, 2:08 PM

New?

Jj0rge @akdev huh, this just happened: https://github.com/ublue-os/main/issues/132

A

akdev•5/18/23, 2:17 PM

huh easiest way to confirm would to be mount to iso and search there

A

akdev•5/18/23, 2:18 PM

you can use github.dev to search in the codebase itself, I've found github code search to not be good with partial searches

A

akdev•5/18/23, 2:41 PM

ostree-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.

Jj0rge @bsherman @Arcitec README ready to go? I PRed the markdown syntax fix just now

B

bsherman•5/18/23, 4:40 PM

new akmods key testing results in https://github.com/ublue-os/nvidia/issues/100

Aakdev > ostree-unverified-registry:quay.io/exampleos/custom:latest - this will pull fr...

J

j0rgeOP•5/18/23, 5:57 PM

found it, it's the iso

J

j0rgeOP•5/18/23, 5:57 PM

if you if install from the iso and pick kinoite you get ostree-unverified-image and not registry

Jj0rge if you if install from the iso and pick kinoite you get ostree-unverified-image ...

B

bsherman•5/18/23, 6:30 PM

did you find where? i'm looking now

J

j0rgeOP•5/18/23, 6:32 PM

that was my next question, where do I look?

Jj0rge that was my next question, where do I look?

B

bsherman•5/18/23, 6:40 PM

yeah, i'm confused, too

main

main

's "release-please" workflow is what builds an ISO

but it uses the

isogenerator

isogenerator

and i don't see

docker:

docker:

anywhere in isogenerator code (local git checkout grep) and only one not-related occurance in

main

main

J

j0rgeOP•5/18/23, 6:41 PM

should we try respinning a release?

Jj0rge should we try respinning a release?

B

bsherman•5/18/23, 6:45 PM

first, when you say you found it, you mean, you did a test install and reproduced?

Jj0rge that was my next question, where do I look?

A

akdev•5/18/23, 6:56 PM

This would be in the grub.cfg in isogenerator

Jj0rge found it, it's the iso

A

akdev•5/18/23, 6:57 PM

Where do you see the mistake?

A

akdev•5/18/23, 6:57 PM

Is it in the grub command line?

J

j0rgeOP•5/18/23, 6:57 PM

how do I find that?

J

j0rgeOP•5/18/23, 6:57 PM

the system boots and can't update basically

A

akdev•5/18/23, 6:58 PM

Type "e" to edit

A

akdev•5/18/23, 6:58 PM

While you have the problematic boot entry selected

A

akdev•5/18/23, 6:58 PM

Wait the system boots or the installer doesn't work?

B

bsherman•5/18/23, 6:58 PM

this file https://github.com/ublue-os/isogenerator/blob/main/installer/overlay/x86_64/EFI/BOOT/grub.cfg

P

pythoner6•5/18/23, 6:58 PM

I'm assuming most relevantly https://github.com/ublue-os/isogenerator/blob/main/installer/overlay/x86_64/EFI/BOOT/grub.cfg#L51

B

bsherman•5/18/23, 6:58 PM

but it's all templates, so

A

akdev•5/18/23, 6:59 PM

in that file we pass

imgurl

imgurl

P

pythoner6•5/18/23, 6:59 PM

Which is used here https://github.com/ublue-os/isogenerator/blob/111381f493c913aaddbc82801ab1f0bacbc8deeb/installer/kickstart/pre-install.sh#L19

A

akdev•5/18/23, 6:59 PM

imageurl=ghcr.io/{{ GITHUB_REPOSITORY_OWNER }}/{{ flavor_menu.label }}:{{ RELEASE }}

imageurl=ghcr.io/{{ GITHUB_REPOSITORY_OWNER }}/{{ flavor_menu.label }}:{{ RELEASE }}

P

pythoner6•5/18/23, 6:59 PM

But I'd assume it's the kickstart/anaconda/whatever that's actually setting the full thing with ostree-unverified-xxx

B

bsherman•5/18/23, 7:00 PM

yep, it's not our templating or boot menu

A

akdev•5/18/23, 7:00 PM

yeah we just pass that to

ostreecontainer --url=

ostreecontainer --url=

B

bsherman•5/18/23, 7:01 PM

so maybe a new build COULD help? if ostreecontainer stuff has an upstream update

B

bsherman•5/18/23, 7:01 PM

i want to reproduce the problem though, before making changes

A

akdev•5/18/23, 7:01 PM

is the problem we are having while installing or does it show after installing?

A

akdev•5/18/23, 7:02 PM

could someone verify the following:

1. download current iso
2.

mount -o loop $theiso

mount -o loop $theiso

3. check the generated grub.cfg, BOOT.conf files
4. check generated pre-install.sh script

B

bsherman•5/18/23, 7:03 PM

yep

B

bsherman•5/18/23, 7:07 PM

from

grub.cfg

grub.cfg

sample kinoite line

linux /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-E-dvd-x86_64-38 nomodeset rd.live.check quiet inst.ks=hd:LABEL=Fedora-E-dvd-x86_64-38:/kickstart/ublue-os-nvidia.ks imageurl=ghcr.io/ublue-os/kinoite-nvidia:38

linux /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-E-dvd-x86_64-38 nomodeset rd.live.check quiet inst.ks=hd:LABEL=Fedora-E-dvd-x86_64-38:/kickstart/ublue-os-nvidia.ks imageurl=ghcr.io/ublue-os/kinoite-nvidia:38

linux /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-E-dvd-x86_64-38 nomodeset rd.live.check quiet inst.ks=hd:LABEL=Fedora-E-dvd-x86_64-38:/kickstart/ublue-os-nvidia.ks imageurl=ghcr.io/ublue-os/kinoite-nvidia:38

linux /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-E-dvd-x86_64-38 nomodeset rd.live.check quiet inst.ks=hd:LABEL=Fedora-E-dvd-x86_64-38:/kickstart/ublue-os-nvidia.ks imageurl=ghcr.io/ublue-os/kinoite-nvidia:38

B

bsherman•5/18/23, 7:08 PM

and from

pre-install.sh

pre-install.sh

ostreecontainer --url="${URL}" --no-signature-verification

ostreecontainer --url="${URL}" --no-signature-verification

B

bsherman•5/18/23, 7:08 PM

I really starting the think the user in the bugreport has an old copy of ISO

B

bsherman•5/18/23, 7:08 PM

because this bug DID exist in past but was fixed, right?

A

akdev•5/18/23, 7:08 PM

yeah it did

A

akdev•5/18/23, 7:08 PM

mm we could ask them for an md5 hash of the iso

B

bsherman•5/18/23, 7:09 PM

i'll do a test install

Aakdev is the problem we are having while installing or does it show after installing?

J

j0rgeOP•5/18/23, 7:12 PM

it installs but subsequent Discover (the kde app) crashes if it's on -image

J

j0rgeOP•5/18/23, 7:13 PM

https://github.com/ublue-os/main/issues/132 is what we have rn

GitHub

Plasma Discover invalid reference for OCI when installed using the ...

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...

J

j0rgeOP•5/18/23, 7:13 PM

I only fired up the VM today but in and out with calls for a while

Jj0rge it installs but subsequent Discover (the kde app) crashes if it's on -image

A

akdev•5/18/23, 7:14 PM

mm in that case I think isogenerator is out of the woods

J

j0rgeOP•5/18/23, 7:15 PM

yeah I have only chosen it on boot, installed it, and I did the status

B

bsherman•5/18/23, 7:16 PM

whoa. WTF

A

akdev•5/18/23, 7:17 PM

You were able to reproduce?

B

bsherman•5/18/23, 7:17 PM

  ostree-unverified-image:docker://ghcr.io/bsherman/silverblue-nvidia-custom:latest
                   Digest: sha256:8e010a07aca4840235411cbc91b1b05a2e37f18fe871730d2253eb291f270e40
                  Version: 38.20230515.0 (2023-05-15T06:27:38Z)
                Initramfs: --force-add tpm2-tss
                   Pinned: yes

  ostree-unverified-registry:ghcr.io/bsherman/silverblue-nvidia-custom:38
                   Digest: sha256:062f55b62ae5c42bf2ed86f5057072b33514e332956ccc926f699c02b7779d2d
                  Version: 38.20230504.0 (2023-05-05T07:23:43Z)
                Initramfs: --force-add tpm2-tss
                   Pinned: yes

  ostree-unverified-image:docker://ghcr.io/bsherman/silverblue-nvidia-custom:latest
                   Digest: sha256:8e010a07aca4840235411cbc91b1b05a2e37f18fe871730d2253eb291f270e40
                  Version: 38.20230515.0 (2023-05-15T06:27:38Z)
                Initramfs: --force-add tpm2-tss
                   Pinned: yes

  ostree-unverified-registry:ghcr.io/bsherman/silverblue-nvidia-custom:38
                   Digest: sha256:062f55b62ae5c42bf2ed86f5057072b33514e332956ccc926f699c02b7779d2d
                  Version: 38.20230504.0 (2023-05-05T07:23:43Z)
                Initramfs: --force-add tpm2-tss
                   Pinned: yes

  ostree-unverified-image:docker://ghcr.io/bsherman/silverblue-nvidia-custom:latest
                   Digest: sha256:8e010a07aca4840235411cbc91b1b05a2e37f18fe871730d2253eb291f270e40
                  Version: 38.20230515.0 (2023-05-15T06:27:38Z)
                Initramfs: --force-add tpm2-tss
                   Pinned: yes

  ostree-unverified-registry:ghcr.io/bsherman/silverblue-nvidia-custom:38
                   Digest: sha256:062f55b62ae5c42bf2ed86f5057072b33514e332956ccc926f699c02b7779d2d
                  Version: 38.20230504.0 (2023-05-05T07:23:43Z)
                Initramfs: --force-add tpm2-tss
                   Pinned: yes

  ostree-unverified-image:docker://ghcr.io/bsherman/silverblue-nvidia-custom:latest
                   Digest: sha256:8e010a07aca4840235411cbc91b1b05a2e37f18fe871730d2253eb291f270e40
                  Version: 38.20230515.0 (2023-05-15T06:27:38Z)
                Initramfs: --force-add tpm2-tss
                   Pinned: yes

  ostree-unverified-registry:ghcr.io/bsherman/silverblue-nvidia-custom:38
                   Digest: sha256:062f55b62ae5c42bf2ed86f5057072b33514e332956ccc926f699c02b7779d2d
                  Version: 38.20230504.0 (2023-05-05T07:23:43Z)
                Initramfs: --force-add tpm2-tss
                   Pinned: yes

this is my machine... why do i have both URL patterns?

@akdev huh, this just happened: https://github.com/ublue-os/main/issues/132

Similar Threads

Similar Threads

Similar Threads