1Password app nowhere to be found and ISO building
Hi, I have created my custom template based off bazzite-gnome-nvidia-open (https://github.com/michal-grzelak/bazzite-custom-dx) with some dev tools and few apps. One of those apps is 1Password and after installing the OS I cannot find it on the system. Weird thing, I tried to run rpm-ostree install 1password thinking it might not get installed and I get the message saying that it’s already installed (which is kind of expected given the recipe 🙂, see the screenshot).
Also a side question. I generate the ISO using the instruction provided here https://blue-build.org/learn/universal-blue/. I am confused with VARIANT env variable. For my case should it be Bazzite or Silverblue as in example?
Also when I don’t provide VERSION env variable (which is not in example), it tries to generate ISO for version 39 instead of the current 40, which is weird given that current Bazzite is based off v40. I have to manually put 40. Why is that?...
Solution:
The Variant envvar is the installers variant, and selects the branding and functionality of the installer.
invalid signature when validating ASN.1 encoded signature
i've replaced the keys in my repository because i thought something broke and would be a possible solution, then realized nothing was actually broken but it was already too late and have changed them
the images build fine, but when trying to do
rpm-ostree upgrade or rebase to the unverified image, i get error: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: cryptographic signature verification failed: invalid signature when validating ASN.1 encoded signature
(repo link)...Solution:
I'll copy my answer:
For anyone who encounters this, those are the steps to solve the issue:
Copy new
cosign.pub from your repo to /etc/pki/containers/$your_image_name.pub...
What is a compiler-based build
So I was looking at the docs and saw this big yellow warning on a few modules (
containerfile and copy to be exact) and I wanna know what it means, and most importantly if I can use the modules on GH ActionsSolution:
This is just to distinguish between the legacy build system that was in the UBlue project to our current system.
Entering emergency mode on boot
Hey team,
Every time I turn my computer on, it will give me the "Emergency mode" screen as shown in the attached picture. I have to press Enter, write
systemctl reboot, then it will take me to the regular fedora Grub menu so I can select the second ostree image which works. Note that I did also rebase to the same exact version as the last functional image but still for some reason when I select anything besides the "old" image it won't work.
Any ideas on what might be the problem, and how to fix?
Thanks...