Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

actions-checkout@v1 failure #322

Closed
lrettig opened this issue Jul 27, 2020 · 7 comments
Closed

actions-checkout@v1 failure #322

lrettig opened this issue Jul 27, 2020 · 7 comments
Labels
area/action Relating to running an action kind/bug Something isn't working meta/wontfix This will not be worked on

Comments

@lrettig
Copy link

lrettig commented Jul 27, 2020

Hello,

I have a workflow that contains the following job:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - name: checkout
      uses: actions/checkout@v1
      with:
        ref: master

I get the following error when I try to run this:

[CI/build]   ❌  Failure - checkout
DEBU[0001] The runs.using key must be one of: [docker node12], got
DEBU[0001] The runs.using key must be one of: [docker node12], got
DEBU[0001] The runs.using key must be one of: [docker node12], got
DEBU[0001] The runs.using key must be one of: [docker node12], got
DEBU[0001] The runs.using key must be one of: [docker node12], got
Error: The runs.using key must be one of: [docker node12], got
> act --version
act version 0.2.10

Here's a full log for this job:

> act pull_request -v
...
[CI/build] ⭐  Run checkout
DEBU[0001] Loading slug from git directory '/Users/user/foobar/.git'
DEBU[0001] Found revision: 875ba070d4d469da65d6157723cb1a93d96f9c23
DEBU[0001] Loading revision from git directory '/Users/user/foobar/.git'
DEBU[0001] Found revision: 875ba070d4d469da65d6157723cb1a93d96f9c23
DEBU[0001] HEAD points to '875ba070d4d469da65d6157723cb1a93d96f9c23'
DEBU[0001] HEAD matches refs/heads/update-go-version
DEBU[0001] using github ref: refs/heads/update-go-version
[CI/build]   ☁  git clone 'https://github.com/actions/checkout' # ref=v1
[CI/build]   cloning https://github.com/actions/checkout to /Users/user/.cache/act/actions-checkout@v1
[CI/build] Cloned https://github.com/actions/checkout to /Users/user/.cache/act/actions-checkout@v1
[CI/build] Checked out v1
DEBU[0001] Read action &{Checkout  Checkout a Git repository. map[clean:{If true, execute `execute git clean -ffdx && git reset --hard HEAD` before fetching false true} fetch-depth:{The depth of commits to ask Git to fetch; defaults to no limit false } lfs:{Whether to download Git-LFS files; defaults to false false } path:{Optional path to check out source code false } ref:{Ref to checkout (SHA, branch, tag) false } repository:{Repository name false } submodules:{Whether to include submodules: false to exclude submodules, true to include only one level of submodules, or recursive to recursively clone submodules; defaults to false false } token:{Access token for clone repository false }] map[] { map[]   [] []} { }} from '/Users/user/.cache/act/actions-checkout@v1/action.yml'
DEBU[0001] About to run action &{Checkout  Checkout a Git repository. map[clean:{If true, execute `execute git clean -ffdx && git reset --hard HEAD` before fetching false true} fetch-depth:{The depth of commits to ask Git to fetch; defaults to no limit false } lfs:{Whether to download Git-LFS files; defaults to false false } path:{Optional path to check out source code false } ref:{Ref to checkout (SHA, branch, tag) false } repository:{Repository name false } submodules:{Whether to include submodules: false to exclude submodules, true to include only one level of submodules, or recursive to recursively clone submodules; defaults to false false } token:{Access token for clone repository false }] map[] { map[]   [] []} { }}
DEBU[0001] type=3 actionDir=/Users/user/.cache/act/actions-checkout@v1 Workdir=/Users/user/smesh/api ActionCacheDir=/Users/user/.cache/act actionName=actions-checkout@v1 containerActionDir=/actions
[CI/build]   ❌  Failure - checkout
DEBU[0001] The runs.using key must be one of: [docker node12], got
DEBU[0001] The runs.using key must be one of: [docker node12], got
DEBU[0001] The runs.using key must be one of: [docker node12], got
DEBU[0001] The runs.using key must be one of: [docker node12], got
DEBU[0001] The runs.using key must be one of: [docker node12], got
Error: The runs.using key must be one of: [docker node12], got
@benwinding
Copy link

benwinding commented Aug 17, 2020

The error message is very unclear, but it seems to refer to the action (from a step) and it's metadata.yaml file:

If you have access to the action.yaml

runs:
  using: 'docker'

I was able to edit it, because it was a local github action (like this)

@github-actions
Copy link
Contributor

Issue is stale and will be closed in 7 days unless there is new activity

@akielbowicz
Copy link

Had a similar error but on an action that I didn't own :( . Hope that it's resolved with #339

@TAnas0
Copy link

TAnas0 commented Jun 9, 2021

@akielbowicz I don't think it has been resolved with that PR. I am using the currently most recent realease 0.2.22 and still facing the same error on the checkout action.

To be more precise, it is referencing this YAML file https://github.com/actions/checkout/blob/releases/v1/action.yml which is lacking the runs.using attribute.

If you use the v2 in your Github Action YAML (- uses: actions/checkout@v2), you can get rid of the error message.
I am not sure if act wants to support the v1 or if it is relevant to #339, I am leaving this here if someone faces the same issue

@catthehacker catthehacker added area/action Relating to running an action kind/bug Something isn't working meta/wontfix This will not be worked on and removed stale labels Aug 17, 2021
@catthehacker
Copy link
Member

actions/checkout@v1 is using a plugin, which is something exclusive to GitHub runners. There are no plans to support that version since v2 works fine.

@manoadamro
Copy link

same thing today with actions/checkout@v3

@catthehacker
Copy link
Member

Please open new issue which is definitely a different issue

@nektos nektos locked as resolved and limited conversation to collaborators May 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/action Relating to running an action kind/bug Something isn't working meta/wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

6 participants