-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Comments
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) |
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
|
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 |
* 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.
…n on windows. Roll-back actions/checkout version for 32 bit test due to gha / node issue (actions/checkout#1681)
…n on windows. Roll-back actions/checkout version for 32 bit test due to gha / node issue (actions/checkout#1681)
…n on windows. Roll-back actions/checkout version for 32 bit test due to gha / node issue (actions/checkout#1681)
…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)
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.
Does the GitHub runner support this method?
The text was updated successfully, but these errors were encountered: