14 Replies
https://github.com/ublue-os/bazzite/commit/05e7c54d92222db33a52b313f96158b0aec87d57
So after every RUN statement
Bazzite saved about 1GB in space for updates.
I'm curious for packages.json, is it more efficient to do them all as one rpm-install or individually with an ostree container commit?
We are doing that now in main/hwe/bluefin
dang did we accidentally improve the entire project?
Each of them have a singular RUN command with ostree container commit at the end
are you telling me only bazzite has 14 RUN commands?
Bluefin used to
But we are down to a singular one
That would never happen lol
Sounds like we just need to shell out Bazzite.
Could do the steam split as part of that too.
Shorten the build times for Bazzite considerably.
my solution to this is don't have 100 RUN statements, then you don't need to run
ostree container commit a bunch
see the Containerfiles for main/hweyeah, 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.
but I'm glad we found some savings for bazzite, that's 30GB a month per device. 😄
From my experience, you can forgoe cleaning out
/tmp as ostree container commit handles that for you. I've had some problems with things being in /var.
You can also use mounts on the RUN instruction though the current Ubuntu runners have old buildah which doesn't have that feature
ostree container commit will essentially ignore mounted dirs
Just tried removing the tmpfs mount I had for /var, seems as though the builds are working properly now with the commit. I was probably doing something weird back thenThis is amazing!