Current Situation:

• When building locally, Docker takes advantage of a cache system to avoid needlessly re-downloading identical dependencies. Building on CI uses no such system, resulting in repeatedly re-downloading identical dependencies, wasting time during the build process.

Goal:

• Building on CI, particularly on test branches, should use a cache system, for the sake of both expediency and efficiency.

Acceptance Criteria:

• Docker builds on CI use a cache system

[optional] Notes:

• pushing and pulling from the GHCR might be enough to implement such a cache

[optional] Open Questions:

• Are there any known issues with Docker's cache implementation that would indicate we should avoid using it for the release builds?
  • we have the option to bypass the cache with ./build.sh --no-cache if we want to be on the safe side