I wouldn't suggest using nvidia without a DE, if you want a custom WM setup, make a custom image. If
I wouldn't suggest using nvidia without a DE, if you want a custom WM setup, make a custom image. If you want a server, use ucore or coreOS
MI downloaded from github.com/ublue-os/main/releases
Gmain-nvidia is supposed to be a baseline for derivative images, such as bluefin, silverblue, etc
MAnd how can i create custom image?
MBut same error with main image
G
MThanks
GAnd #
custom-image-support
custom-image-supportGGitHub
Starting point for making your own OS image. Contribute to ublue-os/startingpoint development by creating an account on GitHub.
MThanks
Gatm starting point is went through a massive rewrite, so I'd suggest waiting a bit longer, all of the work is done, just needs to be approved and merged
WUgh I am both excited and annoyed, I just got all my stuff to where I want it and now imma have to change it all 
MCan i use bazzite with hyprland?
KThere's no existing build for that, but one could be made for the desktop build without too much effort
MOh thanks
MI want to use bazzite for gaming but i want to use hyprland
Kif you have anotherh hyprland image
Kyou can just use bazzite-arch in it
Kin distrobox
Xyeah
Xoh it looked like your review would have an impact too
Xbut apparently not
GIt would be a bit of work
GHyprland doesn't use XDG autostart and doesn't have the same feature set as an actual desktop
GI've made a Hyprland spin before, not hard, just need to enable the copr
Kdeck version certainly
Kdesktop version not so much
Ksince it's just steam in a distrobox
GAh
GYou'd need to figure out yafti
Kfor a proper hyprland bazzite you'd need to port system76's scheduler over as well
Kno idea if hyprland has a plugin system
GThey do
Kbut for personal use, honestly just add distrobox and install bazzite-arch
GIt uses lua
Kmuch easier than your own spin
GYeah I'd just use starting point and extend uBlue main
GThen just install bazzite-arch
B@KyleGospo i've tried to use your trick of using the
COPY command based on $image_name to copy certain files for specific image. Only problem is that I have more images than folders to copy. So at some point builds will fail as they cannot copy a non existent folder. Do you maybe have a good solution for that? My thoughts where to maybe copy them first to /tmp and then copy them via the RUN if grep image_name is "silverblue" then cp /tmp/siverblue / because /tmp is cleand up any way. Would something like that make sense?KCan you send me your container file so I can give you the best possible recommendation?
BKThank you, take a look at this as soon as I can
BThe pull request that is open there will add everything that would go in a specific silverblue image for example. and would now also polluting other images if that goes in. To give an extra idea of what is going on
Bthanks for taking a look when you have time, appreciate it
MI finished configuring my custom image
MAnd how to create ublue image?
KAre you going to have anything big in those image specific folders?
KOr is it mostly just bash scripts and configuration stuff?
Bno just configs, for specific images, maybe a service file if needed, backgrounds maybe if location matters. for this is an example of stuff what should go in silverblue specific image https://github.com/ublue-os/framework/pull/10/files
BBut those doesn't make sense in any other image like kinoite or any other non gnome image
KI would go with the solution we landed on prior to the one we ultimately went with
