During startup, OO consumes a massive amount of CPU for re-generating fonts and themes.
There's an option to disable CPU-heavy tasks on startup which we could make use of.
Not sure about the downsides of this though.
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
I remember that Drebs disabled font generation in his custom OO image some while ago. I can try to find that and maybe ask him about his experience.
If we don't find any obstacle with this we should enable it generally, not only in CI
The needed files will be generated when the container starts. This is not ideal because generation takes time, but is a workaround upstream implements to make it so people can add their fonts to the pre-built images.
If you don't need this feature, you can skip font generation by running the container with SKIP_FONTS_GENERATION=true environment variable. Just add it to the .venv file in the root of the repository prior to starting containers with docker-compose.