Extract apt cache for re-use in next build #316
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Downloading apt packages every time takes a considerable amount of time (This varies based on individual connection speeds). Here we extract the downloaded package indizes as well as the package cache itself and store it outside of the docker image in the ./cache directory. The build script is set up to reload this folder on the next build and re-use the package files. In CI the folder is mounted to the namespace cache volume for re-use in other runs.
Additionally apt workflows are updated so that only a single apt update in the beginning is executed and caches are reused throughout the build. This leads to a larger docker image size (due to multiple versions of the caches in the different layers), but has no influence on the final agnos image size.