JJSo after every RUN statement
NBazzite saved about 1GB in space for updates.
JI'm curious for packages.json, is it more efficient to do them all as one rpm-install or individually with an ostree container commit?
MWe are doing that now in main/hwe/bluefin
Jdang did we accidentally improve the entire project?
MEach of them have a singular RUN command with ostree container commit at the end
Kare you telling me only bazzite has 14 RUN commands?
MBluefin used to
MBut we are down to a singular one
NThat would never happen lol
NSounds like we just need to shell out Bazzite.
NCould do the steam split as part of that too.
NShorten the build times for Bazzite considerably.
Bmy solution to this is don't have 100 RUN statements, then you don't need to run
ostree container commitsee the Containerfiles for main/hwe
Jyeah, not sure if we need the manual cleaning out part of the directories but that also shouldn't matter. When we started the project the docs weren't so clear about where we should be putting the ostree container commit.
Jbut I'm glad we found some savings for bazzite, that's 30GB a month per device. 
LFrom my experience, you can forgoe cleaning out
/tmpostree container commit/varYou can also use mounts on the
RUN instruction though the current Ubuntu runners have old buildah which doesn't have that featureLostree container commitJust tried removing the tmpfs mount I had for
/var
EThis is amazing!
