Closed ghost closed 9 months ago
I used docker/build-push-action@2 to cache my docker images in github action cache. the problem arose when I use ubuntu-latest runner. but I want to create and cache linux/arm64 image.
docker/build-push-action@2
ubuntu-latest
name: Cache Docker layers uses: actions/cache@v2 with: path: /tmp/.buildx-cache key: ${{ runner.os }}-multi-buildx-${{ github.sha }} restore-keys: | ${{ runner.os }}-multi-buildx
name: Build production image uses: docker/build-push-action@v2 with: context: . platform: linux/arm64 builder: ${{ steps.buildx.outputs.name }} push: true tags: ${{ steps.prep.outputs.tagged_image }} cache-to: type=local,mode=max,dest=/tmp/.buildx-cache-new
name: Move cache run: | rm -rf /tmp/.buildx-cache mv /tmp/.buildx-cache-new /tmp/.buildx-cache
linux/amd65 :thinking:
linux/amd65
linux/amd65 thinking
thanks, it corrected
Hi
I used
docker/build-push-action@2
to cache my docker images in github action cache. the problem arose when I useubuntu-latest
runner. but I want to create and cache linux/arm64 image.name: Cache Docker layers uses: actions/cache@v2 with: path: /tmp/.buildx-cache key: ${{ runner.os }}-multi-buildx-${{ github.sha }} restore-keys: | ${{ runner.os }}-multi-buildx
name: Build production image uses: docker/build-push-action@v2 with: context: . platform: linux/arm64 builder: ${{ steps.buildx.outputs.name }} push: true tags: ${{ steps.prep.outputs.tagged_image }} cache-to: type=local,mode=max,dest=/tmp/.buildx-cache-new
name: Move cache run: | rm -rf /tmp/.buildx-cache mv /tmp/.buildx-cache-new /tmp/.buildx-cache
Behaviour
Steps to reproduce this issue
Expected behaviour