Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Reuse BuildKit cache in release Docker builds

Closed Beginner friendly
  • Is something wrong?
#126 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #139 by @MathijsNabbe — closed without merging
  • #141 by @MathijsNabbe — merged

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
73/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
docker, github-actions
Domain
ci-cd, devops

Research direction

Read .github/workflows/docker.yml for the existing image-specific cache scopes, then find the release workflow's docker/build-push-action steps. Add matching cache-from and cache-to settings for each image, run a repeated release build to confirm cache hits and correctness, and compare build durations while accounting for cache export time.

Written by the indexing model from the issue text.

Description

Summary

The release workflow builds and pushes all three images, but its docker/build-push-action steps do not configure cache-from or cache-to. The CI Docker workflow already uses the GitHub Actions BuildKit cache, so release builds can repeat dependency restore and compilation work.

Proposed change

Add per-image GitHub Actions cache import/export to the release workflow, using the same image-specific scopes as .github/workflows/docker.yml:

cache-from: type=gha,scope=${{ matrix.image }}
cache-to: type=gha,mode=max,scope=${{ matrix.image }}

Acceptance criteria

  • Release builds import and export a cache per image.
  • Cache scopes match the CI Docker workflow.
  • A repeated build with unchanged inputs shows cache hits and does not regress release correctness.
  • Compare build durations before and after; note that exporting a large cache also has a cost.
Dominant language
C#
Stars
0
Forks
2
Avg merge
5h 1m
Merged PRs (30d)
30

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Dome-Works/DOME

All issues in Dome-Works/DOME

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.