[SOLVED] Question about using template to build my own image

Contributing
1

I have “successfully” built a custom image using the template (the github is: GitHub - whelanh/customBluefinDx: Experiment on building a custom image). I followed the steps to add the co-signing key. However when I attempt a sudo bootc switch ghcr.io/whelanh/custombluefindx:latest, I get the following error:

ERROR Switching: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: unable to retrieve auth token: invalid username/password: unauthorized

I would sincerely appreciate it if anyone can point me in the right direction to correct this. I suspect there is a step I’m missing in perhaps having to register somewhere(?) Sincere thanks…

2

What about using rpm-ostree rebase switch ostree-image-signed:docker://ghcr.io/whelanh/custombluefindx:latest? I know the Bluefin guide uses bootc now, but rpm-ostree rebase may still work…

Ref:

3

Thank you very much for the suggestion. I had tried that (I should have mentioned it), but got a very similar error:

Pulling manifest: ostree-image-signed:docker://ghcr.io/whelanh/custombluefindx:latest
error: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: unable to retrieve auth token: invalid username/password: unauthorized```
4

Looking at the GitHub Actions page, it complained about casing:

Also, I checked at the Packages tab in your repo’s page? If Actions completed correctly, it should output a package, like here in mine:

I checked on a random fork from image-template’s fork list, and it outputted a package too:

I’m currently outside, but I’d recommend comparing the latest successful Actions in both repos with yours. I’m going to go read it through as well, but it might take a while for me since I’m out.

5

I really appreciate your help and will study the differences between yours and mine. Mine did produce a package (https://github.com/whelanh/customBluefinDx/pkgs/container/custombluefindx). Perhaps that casing problem is the root problem though. I will look into it. I did find some references to the possibility that it could be an upstream signing issue (Bluefin update error (failed to invoke method OpenImage)), but that seems unlikely if everyone else isn’t having this problem. :grinning_face_with_smiling_eyes:

6

Perhaps this is the issue? Try setting the package to public, just in case.

1 Like
7

I had a similar issue, and this resolved it. I’d initially set my repository to private, and so the packages it was building were also private.

Setting both repo AND package to Public sorted things out

1 Like
8

Thank you @fenglengshun and @benleolander! That was it. I did the same – initially setting as private github and then changing to public. But the package inherited the old privacy. Thank you both so much!!! This is an amazing project.

2 Likes