CrazyMax

@tonynajjar Just made some tests in this repo as well and looks good: https://github.com/docker/build-push-action/pull/1075

You need to set the `actions/cache` step in our workflow otherwise cache is not retained across runs. See our docs: https://docs.docker.com/build/ci/github-actions/cache/#local-cache Tried in this repo through https://github.com/docker/build-push-action/pull/1066 and looks good...

> `path: ~/.cache/docker-ci` Don't think `actions/cache@v4` expands `~`. You should use an absolute dir.

Maybe cache is being evicted because you exceed storage limit: https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy > GitHub will remove any cache entries that have not been accessed in over 7 days. There is no...

Sounds like a registry configuration. Tag immutability is probably turned on for this repository: https://docs.aws.amazon.com/AmazonECR/latest/userguide/image-tag-mutability.html

@kpcyrd Cache mounts through `--mount=type=cache` are not exported atm. They are just useful for incremental builds. So if you want this to be exported you have to remove this cache...

> Here is a log from when I made a change to the `main.go` file only: > ``` > #9 [5/7] RUN sleep 60; go mod download > #9 sha256:e0d50a7a4a31ddb3684e2758f437fbb9e31dec18fb8857490dfe2178142907a8...

Ok this looks to be regression since BuildKit 0.10, with 0.9.3: ``` #10 [build-image 4/5] RUN --mount=type=bind,source=go.mod,dst=go.mod --mount=type=bind,source=go.sum,dst=go.sum go mod download -x #10 sha256:8e170bdc7a4c121a1f0a5c8f0cc5ffbb2823e26d00cb5d4449b7a8e596ac6908 99B / 99B 0.1s done #10...

@tomasfejfar Yes this is BuildKit related, feel free to open an issue there, thanks!

``` Unavailable desc = error reading from server: EOF ``` Might be an issue with your registry. Can you post the BuildKit logs please? See https://docs.docker.com/build/ci/github-actions/configure-builder/#buildkit-container-logs