fix(docker): use scope instead of ref for GHA cache backend#1213
Merged
int128 merged 2 commits intoint128:mainfrom Jan 11, 2026
Merged
fix(docker): use scope instead of ref for GHA cache backend#1213int128 merged 2 commits intoint128:mainfrom
scope instead of ref for GHA cache backend#1213int128 merged 2 commits intoint128:mainfrom
Conversation
When using the GitHub Actions (GHA) cache backend, the use of useless tags `ref=` leads to cache collisions between different builds, branches, and stages due to the shared default namespace (buildkit). This change replaces `ref=` with `scope=` when the cache type is `gha`, as recommended by the official Docker documentation: https://docs.docker.com/build/cache/backends/gha/#scope Using `scope=` ensures proper cache isolation and prevents unintended invalidation, significantly improving cache reliability.
NikitaCOEUR
added a commit
to Groupe-Hevea/ci-github-container
that referenced
this pull request
Jul 31, 2025
This commit introduces a workaround for the GitHub Actions cache backend when using the docker `cache-from` and `cache-to` flags with BuildKit. The current version of `int128/docker-build-cache-config-action` incorrectly uses `ref=` instead of `scope=` for the `gha` cache backend, which leads to shared caches across branches and builds, resulting in frequent invalidations and inefficient caching. Until the upstream PR is merged and released: int128/docker-build-cache-config-action#1213 ...this commit replace `ref=` by `scope=` to ensure proper cache isolation and reliable cache behavior in CI. This workaround will be removed once the upstream fix is available in a stable release.
Contributor
|
@int128 can you check this PR please? It's a good one IMO! |
Contributor
|
Hi @int128, kindly reminder, can you have a look at this PR please? |
Contributor
|
Hi @int128, here is my monthly kindly reminder, I you can have a look to this PR please. |
neilime
pushed a commit
to hoverkraft-tech/ci-github-container
that referenced
this pull request
Sep 30, 2025
This commit introduces a workaround for the GitHub Actions cache backend when using the docker `cache-from` and `cache-to` flags with BuildKit. The current version of `int128/docker-build-cache-config-action` incorrectly uses `ref=` instead of `scope=` for the `gha` cache backend, which leads to shared caches across branches and builds, resulting in frequent invalidations and inefficient caching. Until the upstream PR is merged and released: int128/docker-build-cache-config-action#1213 ...this commit replace `ref=` by `scope=` to ensure proper cache isolation and reliable cache behavior in CI. This workaround will be removed once the upstream fix is available in a stable release.
Contributor
|
Hi @int128, any change to get this PR review / merged? Thanks |
Contributor
|
Hi @int128, Thanks |
int128
approved these changes
Jan 11, 2026
Owner
int128
left a comment
There was a problem hiding this comment.
Looks good. Sorry for the late reply.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request updates the
generateDockerFlagsfunction and its associated tests to dynamically determine the correct key (scopeorref) for Docker cache flags based on thecacheTypeinput. This improves flexibility and ensures compatibility with different cache types.Updates to
generateDockerFlagsfunction:generateDockerFlagsfunction insrc/docker.tsto use a dynamic key (refKey) for cache flags, which is set toscopeifcacheTypeisgha, andrefotherwise. This change affects bothcacheFromandcacheToflag generation. [1] [2]Updates to tests:
tests/docker.test.tsto reflect the new behavior of thegenerateDockerFlagsfunction, verifying that the correct key (scopeorref) is used in the generated cache flags.Context
When using the GitHub Actions (GHA) cache backend, the use of useless tags
ref=leads to cache collisions between different builds, branches, and stages due to the shared default namespace (buildkit).This change replaces
ref=withscope=when the cache type isgha, as recommended by the official Docker documentation: https://docs.docker.com/build/cache/backends/gha/#scopeUsing
scope=ensures proper cache isolation and prevents unintended invalidation, significantly improving cache reliability.