GitHub Actions Cache - Docker Build

[ajithshah]

This legacy service is shutting down, effective April 15, 2025. Migrate to the new service ASAP

ERROR: This legacy service is shutting down, effective April 15, 2025. Migrate to the new service ASAP. For more information: https://gh.io/gha-cache-sunset

ERROR: failed to solve: This legacy service is shutting down, effective April 15, 2025. Migrate to the new service ASAP. For more information: https://gh.io/gha-cache-sunset
Reference
Check build summary support

      - name: Docker Build and Push
        uses: docker/build-push-action@v6
        with:
          context: .
          file: ${{ inputs.dockerfile }}
          push: true
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}
          platforms: ${{ inputs.docker_image_platforms }}
          build-args: |
            IMAGE_TAG=${{ steps.meta.outputs.tags }}
          cache-from: type=gha
          cache-to: type=gha,mode=max
          github-token: ${{ secrets.TOKEN_GITHUB }}

[andrewhharmon]

is this indicating version 3.2.4 of actions/cache is being used and this indicates that it's deprecated?

Editing this out, as I linked to the action instead of the node library

[newman-dani]

I was able to bypass the error by setting no-cache: true but it does increase an action execution time.

UPD.
Started to fail again

[patbernard]

is this indicating version 3.2.4 of actions/cache is being used and this indicates that it's deprecated?

If you look at the latest release for v6, it's pointing to 4.0.2 - which should be fine: https://github.com/docker/build-push-action/blob/v6.15.0/yarn.lock

Edit: @bradley-yoo-anrok good catch. The latest version of build-push-action is pinned to a deprecated version. I was under the impression that v4.* was okay from this notice: https://github.blog/changelog/2025-01-15-github-actions-ubuntu-20-runner-image-brownout-dates-and-other-breaking-changes/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

But that scope is obviously larger than the original notice now.

[newman-dani]

@patbernard I do use 471d1dc4e07e5cdedd4c2171150001c434f0b7a4 # v6.15.0 and still getting it.

[bradley-yoo-anrok]

I don't think 4.0.2 is fine. if you look at the original deprecation notice, 4.1.2 is deprecated.

I can't believe the github's own decomission notice contains examples of upgrades that doesn't work.

[andrewhharmon]

yes we tried v6 and still got it as well

[mmckane]

I also tried V6 and am seeing this happen

[andrewhharmon]

I think this is the package being used here. it says v4.0.0 should be good.

[mmckane]

if it helps I am using docker/setup-buildx-action@v3 as well

[trautonen]

I'm using the latest docker/setup-buildx-action@v3 which yarn.lock currently points to

"@actions/cache@npm:^4.0.2":
  version: 4.0.2
  resolution: "@actions/cache@npm:4.0.2"

and the builds are failing

[jpugliesi]

Buildkit v0.20+ recently upgraded GHA Cache support to v2: moby/buildkit#5683

But Github's deprecation notice shows version <4.0 will are being deprecated

[aarashy]

Anybody know if its possible to use runs-on instead? We like this cache way better

[johnfountainsomos]

Buildkit v0.20+ fixes this: moby/buildkit#5683

You can upgrade by updating the docker/setup-buildx-action that's commonly run before this build-push-action:

- uses: docker/setup-buildx-action@v3
  with:
    version: v0.20.0

this did not work for us. still the same failure

[jpugliesi]

Buildkit v0.20+ fixes this: moby/buildkit#5683
You can upgrade by updating the docker/setup-buildx-action that's commonly run before this build-push-action:

- uses: docker/setup-buildx-action@v3
  with:
    version: v0.20.0

this did not work for us. still the same failure

Indeed - v0.20 upgrades to cache API v2, while cache <v4.0 is being deprecated - updated my comment