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

exec /__e/node20/bin/node: no such file or directory #1681

Open
twmht opened this issue Apr 11, 2024 · 3 comments
Open

exec /__e/node20/bin/node: no such file or directory #1681

twmht opened this issue Apr 11, 2024 · 3 comments

Comments

@twmht
Copy link

twmht commented Apr 11, 2024

on:
  pull_request:
    types: [opened, synchronize]

name: Tag Created

jobs:
  tag-created:
    runs-on: rtx4090-1
    container:
      image: nvcr.io/nvidia/l4t-tensorrt:r8.0.1-runtime

    steps:
      - name: Checkout code
        uses: actions/checkout@v4
        with:
          ref: v0.2.0
...

I am trying to do cross-compilation. The self-hosted runner is x86-64, but the Docker image is arm64. However, I am encountering the following error.

Run actions/checkout@v4
  with:
    ref: v0.[2](https://github.com/TechWhiskers/fastflow_core/actions/runs/8644594833/job/23700048482#step:3:2).0
    repository: TechWhiskers/fastflow_core
    token: ***
    ssh-strict: true
    persist-credentials: true
    clean: true
    sparse-checkout-cone-mode: true
    fetch-depth: 1
    fetch-tags: false
    show-progress: true
    lfs: false
    submodules: false
    set-safe-directory: true
/usr/bin/docker exec  0[3](https://github.com/TechWhiskers/fastflow_core/actions/runs/8644594833/job/23700048482#step:3:3)0cae08918d43e6cbb15a[4](https://github.com/TechWhiskers/fastflow_core/actions/runs/8644594833/job/23700048482#step:3:4)a5b7b1b192276fc6a65970291c246d34a8349c3a0 sh -c "cat /etc/*release | grep ^ID"
exec /__e/node20/bin/node: no such file or directory

Does the GitHub runner support this method?

@cory-miller
Copy link
Contributor

What version is the Actions Runner software in that image? Can you confirm it supports Node 20 (version must be >= https://github.com/actions/runner/releases/tag/v2.308.0)

@skyzyx
Copy link

skyzyx commented Jun 26, 2024

I know that this is old, but we're running GHES 3.12.5 and our self-hosted runners are using the v2.316.1 release. This only seems to occur when a job is running inside a custom Docker container. While the workflow log says that /__e/ is mounted as expected, the error message is still common in these scenarios.

exec /__e/node20/bin/node: no such file or directory

@tfpf
Copy link

tfpf commented Jun 30, 2024

This happens with GitHub-hosted runners, too.

jobs:
  build_other:
    name: build on ${{ matrix.arch }}/debian:12
    runs-on: ubuntu-22.04
    container: ${{ matrix.arch }}/debian:12
    strategy:
      matrix:
        arch: [i386, amd64]
    steps:
      - uses: actions/checkout@v4

The first job (on i386/debian:12) fails with the error in the title; the second (on amd64/debian:12) checks out the code successfully.

tfpf added a commit to tfpf/dotfiles that referenced this issue Jul 1, 2024
* Separated Linux build jobs from macOS and Windows build jobs.
  * 32-bit binaries for Linux must be built in a 32-bit container. I used Debian.
  * Hence, it made sense to use a 64-bit Debian container to build the 64-bit binaries, ditching Ubuntu.
* Used older versions of the checkout and upload actions for Linux builds.
  * The newer versions don't work in containers.
    * actions/runner#2115
    * actions/upload-artifact#361
    * actions/checkout#1681
  * Consequently, the an older version of the corresponding download action must be used.
  * The older upload action doesn't recognise wildcard patters, so specified the `bin` directory to upload.
  * Did the same for the newer upload action for consistency.
* Moved `env` next to the step which requires the token.
* Tried to build the binaries in ARM containers, but the Linux runner is an AMD64 machine, so it didn't work.
  * The macOS runner which is an ARM machine does not have Docker, so couldn't use it, either.
pauldmccarthy added a commit to effigies/indexed_gzip that referenced this issue Jul 16, 2024
…n on

windows. Roll-back actions/checkout version for 32 bit test due to gha / node
issue (actions/checkout#1681)
pauldmccarthy added a commit to effigies/indexed_gzip that referenced this issue Jul 16, 2024
…n on

windows. Roll-back actions/checkout version for 32 bit test due to gha / node
issue (actions/checkout#1681)
pauldmccarthy added a commit to effigies/indexed_gzip that referenced this issue Jul 16, 2024
…n on

windows. Roll-back actions/checkout version for 32 bit test due to gha / node
issue (actions/checkout#1681)
pauldmccarthy added a commit to effigies/indexed_gzip that referenced this issue Jul 16, 2024
…to be

available??). Update zlib version on windows. Roll-back actions/checkout
version for 32 bit test due to gha / node
issue (actions/checkout#1681)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants