chore(ci): enable BuildKit cache in Docker workflow #667
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.
Summary
Enable GitHub Actions BuildKit cache for the nethermind Docker build to
reduce build times and improve CI performance.
Details
.github/workflows/docker.yml:cache-from: type=ghaandcache-to: type=gha,mode=maxto thedocker/build-push-actionstep for thenethermindimage.According to Docker's cache management docs, using the GitHub Actions cache
backend for BuildKit allows reusing previously built layers between runs,
which speeds up subsequent builds.
Testing
The workflow still builds and pushes the
nethermindimage; behavior isunchanged except for improved caching.