docker / setup-buildx-action

GitHub Action to set up Docker Buildx
https://github.com/marketplace/actions/docker-setup-buildx
Apache License 2.0
906 stars 142 forks source link

Error: The runs.using key in action.yml must be one of: [composite docker node12 node16], got node20 #278

Closed mconigliaro closed 8 months ago

mconigliaro commented 9 months ago

Contributing guidelines

I've found a bug, and:

Description

Error: The runs.using key in action.yml must be one of: [composite docker node12 node16], got node20

Expected behaviour

I expected not to get an error message

Actual behaviour

I get an error message

Repository URL

No response

Workflow run URL

No response

YAML workflow

name: Docker build and push

on:
  workflow_call

jobs:
  build-push:
    runs-on: ubuntu-latest

    steps:
      - uses: docker/setup-buildx-action@v3

Workflow logs

$ act --env-file .env.ephemeral -W .github/workflows/docker-build-push.yml
[Docker build and push/build-push] šŸš€  Start image=catthehacker/ubuntu:act-latest
[Docker build and push/build-push]   šŸ³  docker pull image=catthehacker/ubuntu:act-latest platform= username= forcePull=true
[Docker build and push/build-push]   šŸ³  docker create image=catthehacker/ubuntu:act-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[]
[Docker build and push/build-push]   šŸ³  docker run image=catthehacker/ubuntu:act-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[]
[Docker build and push/build-push]   ā˜  git clone 'https://github.com/docker/setup-buildx-action' # ref=v3
[Docker build and push/build-push] šŸ  Job succeeded
Error: The runs.using key in action.yml must be one of: [composite docker node12 node16], got node20

BuildKit logs

No response

Additional info

No response

mconigliaro commented 9 months ago

Reverting back to docker/setup-buildx-action@v2 seems to work for now.

crazy-max commented 8 months ago

$ act

Same as https://github.com/docker/setup-buildx-action/issues/53, act is not officially supported and therefore might diverge with public runners. In this case they don't seem to support the node20 runtime.