the builds in my copr tune it to use the Linux-TKG CFQ settings instead of Zen
the builds in my copr tune it to use the Linux-TKG CFQ settings instead of Zen
SHey @KyleGospo How would I enable "system76-scheduler", do I just copy the files you mentioned to /usr/etc/... here on my repo?
Kwon't need any files at all, just install from copr and enable the service
Ksee bazzite's containerfile
Sah so they are not needed?
Sthe zram-generator etc.
Sfiles
Kspecifically for system76-scheduler
Kthe others each do their own little things
Sah so they dont "hurt"?
Swhat if i use the recipe.yml file?
Scan i just add them to the dockerfile?
Kyea
Sok good, does the line matter?
Sand exacly what do i add
WA lot of this low level stuff is really new to me.
Sis it just ?
S@KyleGospo
EThat'll do it
Sok good!
EIt's installed right?
Syea
EOkay
Salso
Scould you help with this? https://discord.com/channels/1072614816579063828/1084120222400774325/1134140475272605716
XI was thinking for the system76-scheduler service, does that need to be layered or can it instead run inside a container and by passing through the host dbus socket?
KI haven't tried, but applications like btop work great in a container
Kit's fairly likely it'd work fine
Xit seems to work if I pass
/run/dbus/system_bus_socket/etc/dbus-1/system.d/com.system76.Scheduler.confvery nice
Bthat's pretty cool
KGitHub
Reduce the amount of layers by keeping RUN and COPY to a minimum
Kwould love some extra eyes on this, big change from how we were doing things and I'm only going off what I've read so far regarding layer count & size
JI don't know enough to know other than I am very interested in the resulting difference
KBefore (Saving this for when I can get an after)
message.txt5.45KB
KLayers data for this
message.txt16.93KB
RWhen proper support for handling the OCI layers is implemented in whatever package, wouldn't you want to have multiple layers so you're only pulling the changed layers, rather than everything?
E.g. pulling the 20MB for that added package rather than all 3GB of the image each day
E.g. pulling the 20MB for that added package rather than all 3GB of the image each day
Kthere an issue for this?
Kmuch prefer that
GI'd check out bootc
GIdk if they will do it there but that's the future of ostree native containers
RThe closest I could find:
https://github.com/coreos/rpm-ostree/issues/4012
But I think it's already partially implemented already.
If you add a new package now in a RUN statement at the end of the Containerfile and run
If you bundled all package installs together, you will have to download the entire layer/chunk containing not only your change, but all other packages installed in that layer.
I seem to remember there was some talk about how to handle this better since daily updates (updates in the base image) require the full 3gb or so to be downloaded
https://github.com/coreos/rpm-ostree/issues/4012
But I think it's already partially implemented already.
If you add a new package now in a RUN statement at the end of the Containerfile and run
rpm-ostree updateIf you bundled all package installs together, you will have to download the entire layer/chunk containing not only your change, but all other packages installed in that layer.
I seem to remember there was some talk about how to handle this better since daily updates (updates in the base image) require the full 3gb or so to be downloaded
GitHub
Today, the algorithm backing rpm-ostree compose container-encapsulate (and rpm-ostree compose image) is pretty simplistic. It basically tries to stick the largest RPMs in layers, and then "spi...
Kyeah, right now most updates are 1.5GB which is just massive for the changes being made
Kthat's with it split up though
RI guess that's after the daily rebuilds? Where the base is changed and therefore all subsequent steps have changed - meaning you must download all layers after the changed bit.
I thought there was an issue somewhere about how to prevent this upstream, but couldn't find it
I thought there was an issue somewhere about how to prevent this upstream, but couldn't find it
RI might be wrong with all of this. I'm going off best practices for building images for K8s, which is quite different to what we're doing with bootc or whatever.
J@Gerblesh did you ever figure anything else more about this selinux issue? https://github.com/ublue-os/main/issues/223 i bothered two incorrect upstreams, so i appreciate you filing the issue 
GitHub
this issue is detailing the repeated problems we had with greetd and SELinux in the discord, don't know if this will ever be solved or if it can be solved but it's good to have it as an iss...
GNot really
AThe last error message in that issue can probably be worked around by specifiying the full selinux label the file should have
AThis is probably a bug in rpm-ostree ultimately because the rpm package has the correct things set 
