From 4f388c9b2a522cd75703907f5d15353c4d32012c Mon Sep 17 00:00:00 2001 From: fristyxd Date: Mon, 2 Nov 2026 14:15:37 +0300 Subject: [PATCH] ci(deploy): use the image's buildx instead of setup-buildx-action buildx 0.38.1 is baked into git.fristy.net/actions/runner-images. Creating a docker-container builder with the CLI keeps the registry cache (cache-from/cache-to) working without pulling the action. --- .gitea/workflows/deploy.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/deploy.yaml b/.gitea/workflows/deploy.yaml index 47d3e9d..9ee21d4 100644 --- a/.gitea/workflows/deploy.yaml +++ b/.gitea/workflows/deploy.yaml @@ -30,7 +30,9 @@ jobs: username: ${{ github.actor }} password: ${{ secrets.REGISTRY_TOKEN }} - name: Set up Buildx - uses: docker/setup-buildx-action@v3 + # buildx ships with the runner image; only a builder instance is missing, + # and the docker-container driver is what the registry cache needs. + run: docker buildx create --name ci --driver docker-container --use - name: Resolve tags id: meta uses: docker/metadata-action@v5