You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker Images don't seem to be caching very well when running GitHub actions. Potentially this could be because the base image (spack_packages) is constantly changing and therefore any images on top of it must be rebuilt form scratch.
Make the environment setup (apt-get) it's own image, meaning it will be snapshotted and won't need to be rebuilt.
Determine if there is a need for multiple image layers at all - could we just have an image with all of the models dependencies installed, and use spack activate <model_environment> as a build arg?
Pros: amalgamation into a single image and easy switching between dependencies with spack activate, potential for a bit more build caching
Cons: Every time a model (dependency) is changed, this large one will have to be rebuilt.
The ramblings of a madman...
The text was updated successfully, but these errors were encountered:
Docker Images don't seem to be caching very well when running GitHub actions. Potentially this could be because the base image (spack_packages) is constantly changing and therefore any images on top of it must be rebuilt form scratch.
Investigate possible solutions:
apt-get
) it's own image, meaning it will be snapshotted and won't need to be rebuilt.spack activate <model_environment>
as a build arg?spack activate
, potential for a bit more build cachingThe ramblings of a madman...

The text was updated successfully, but these errors were encountered: