docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

gha: update the repo of buildkit-cache-dance 

https://github.com/overmindtech/buildkit-cache-dance is now archived.

https://github.com/reproducible-containers/buildkit-cache-dance
is the current active fork by myself.

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
This commit is contained in:
Akihiro Suda 2023-09-14 23:44:54 +09:00
parent 11fb85930c
commit 446fcceb4e
No known key found for this signature in database
GPG Key ID: 49524C6F9F638F1A
1 changed files with 7 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
content/build/ci/github-actions/cache.md
View File

@ -137,12 +137,10 @@ jobs:
BuildKit doesn't preserve cache mounts in the GitHub Actions cache by default. BuildKit doesn't preserve cache mounts in the GitHub Actions cache by default.
If you wish to put your cache mounts into GitHub Actions cache and reuse it If you wish to put your cache mounts into GitHub Actions cache and reuse it
between builds, you can use a workaround provided by two third-party actions: between builds, you can use a workaround provided by
[`reproducible-containers/buildkit-cache-dance`](https://github.com/reproducible-containers/buildkit-cache-dance).
- `overmindtech/buildkit-cache-dance/extract` This GitHub Action creates temporary containers to extract and inject the
- `overmindtech/buildkit-cache-dance/inject`
These GitHub Actions creates temporary containers to extract and inject the
cache mount data with your Docker build steps. cache mount data with your Docker build steps.
The following example shows how to use this workaround with a Go project. The following example shows how to use this workaround with a Go project.
@ -183,7 +181,9 @@ jobs:
key: ${{ runner.os }}-go-build-cache-${{ hashFiles('**/go.sum') }} key: ${{ runner.os }}-go-build-cache-${{ hashFiles('**/go.sum') }}
- name: inject go-build-cache into docker - name: inject go-build-cache into docker
uses: overmindtech/buildkit-cache-dance/inject@306d31a77191f643c0c4a95083f36c6ddccb4a16 # v1 was composed of two actions: "inject" and "extract".
# v2 is unified to a single action.
uses: reproducible-containers/buildkit-cache-dance@v2.1.2
with: with:
cache-source: go-build-cache cache-source: go-build-cache
@ -198,15 +198,10 @@ jobs:
tags: ${{ steps.meta.outputs.tags }} tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }} labels: ${{ steps.meta.outputs.labels }}
platforms: linux/amd64,linux/arm64 platforms: linux/amd64,linux/arm64
- name: extract go-build-cache from docker
uses: overmindtech/buildkit-cache-dance/extract@306d31a77191f643c0c4a95083f36c6ddccb4a16
with:
cache-source: go-build-cache
``` ```
For more information about this workaround, refer to the For more information about this workaround, refer to the
[GitHub repository](https://github.com/overmindtech/buildkit-cache-dance). [GitHub repository](https://github.com/reproducible-containers/buildkit-cache-dance).
### Local cache ### Local cache