maybe what you were going to do would require more fine tuning?
maybe what you were going to do would require more fine tuning?
Hi dont know what youre planning to do
DWell my plan is to firstly get rid of all the nvidia-stuff in the build and restrict it to just bazzite-deck builds and ditch everything else. Next is to debloat the build by getting rid of packages that I don't use, and finally, add my own packages to the Containerfile.
Kreally depends on what you're trying to do
DWell my plan is to firstly get rid of all the nvidia-stuff in the build and restrict it to just bazzite-deck builds and ditch everything else. Next is to debloat the build by getting rid of packages that I don't use, and finally, add my own packages to the Containerfile.
Kin this case, since you want to debloat, the realistic option is a fork. You can use startingpoint or even just your own containerfile that does FROM ghcr.io/ublue-os/bazzite
Kbut removing a package will free up zero disk space in that scenario
Kif you don't care about that and simply want them turned off, you can do that
Kand it'll be much easier on you
Hhence why i said in 99% of cases startingpoint is the way to go 
Dyou mean the final image that gets published to ghcr wont be smaller?
Kcorrect
DO_o
Klarger, if anything
DI thought the Container file is building everything from scratch.. or is that not how it works?
Kwe have the same limitation, if I remove something that's included in Silverblue or Kinoite we save no disk space
Kif you're removing something we add, a fork saves you disk space
Ksince it's never added in the first place
DAh right. Well, that suits me fine then 
DNow how do I fix this signing error lol
Kyou need a key pair defined in your github private vars to sign an image
Kyou can either not sign it, or add a key
DI've replaced my cosign.pub and pasted the private key under Secrets > Repository secretes, under the variables SIGNING_SECRET and COSIGN_PRIVATE_KEY. Should I be using Variables instead? As I understand, Variables are plain-text and should't be used for secrets, so not sure where I'm going wrong.
Kublue webite has guides for the latter
Kshould be secret, sec
KSIGNING_SECRETis what it's named
Dyep I've got that
Dit's under "repository secrets"
Kdoes your key have a password?
Dnope
Dalso, the error in the log mentions only
COSIGN_PRIVATE_KEY
Kthis is why
Dhmm. Should I just re-upload my cosign.pub and replace the
SIGNING_SECRETworth a shot
Vquick question, i would like to install bazzite too on my asus zenbook pro duo. hybrid graphics and dual screen laptop.
Vcan i easily add a kernel module? asus-wmi to be exact
Vasus-wmi-screenpad*
Kyou cannot, has to be part of the image
Kis this not included with asus-linux?
Vi don't know, i can't find anything documented related to it tbh
KGitLab
fedpkg --name kernel --namespace rpms --release f38 local --arch x86_64 --without debug --without debuginfo --with release --with headers --without configchecks
K
Kseems like it
Vohh haven't found that link, that's why
Vgreat i'll be installing bazzite on my laptop soon too
Vcurrently running on my desktop and steam deck, would love for my laptop to join the club
D
DAlso, forgot to mention that I've put the secrets under Secrets and Variables > Actions, I assume this is correct and shouldn't be "Codespaces" or "Dependabot"?
D
