v2.312.0 regression : nodeJs not packaged correctly anymore

[odoucet]

Describe the bug
self-hosted runner regression on image v2.312.0 that do not package nodeJS anymore

To Reproduce
The following workflow :

name: Build
jobs:
  build:
    runs-on: arc-runner
    container: docker.io/docker:git
    steps:
      - uses: actions/checkout@v3

leads to following error :

Run actions/checkout@v3
Run '/home/runner/k8s/index.js'
  shell: /home/runner/externals/node16/bin/node ***0***
env: can't execute '/__e/node16/bin/node': No such file or directory
Error: Error: failed to run script step: command terminated with non-zero exit code: exit status 127
Error: Process completed with exit code 1.
Error: Executing the custom container implementation failed. Please contact your self hosted runner administrator.

Expected behavior

Run actions/checkout@v4.1.1
Run '/home/runner/k8s/index.js'
Syncing repository: xxx/xxxxx
Getting Git version info
[...]

Runner Version and Platform

Version of your runner? ghcr.io/actions/actions-runner:v2.312.0
OS of the machine running the runner? Linux Kubernetes 1.26.11

Forcing image v2.311.0 makes it work again, so it's definitely a regression in latest image.

What's not working?

It seems nodeJS path is not correct anymore in image, and is faling with actions/checkout@v3 (also with actions/checkout@v4.1.1)

Job Log Output

see up.

Runner and Worker's Diagnostic Logs

nothing relevant.

[gmmcal]

Also having the same problem

[gmmcal]

And also confirm that rolling back to 2.311.0 fixes the problem. spot on report @odoucet

[TingluoHuang]

I pull down the image and verity the binary is there.

@nikola-jokic is this a problem with the latest container hook version (0.5.0)?

[gmmcal]

any updates on this?

[TingluoHuang]

We revert the change and re-publish the image without the updated container hook.
#3101

[gmmcal]

Ohh so 2.312.0 is stable and healthy?

[TingluoHuang]

Ohh so 2.312.0 is stable and healthy?

It should now.

[gmmcal]

nice! will test tomorrow and report back.

[cgundy]

Is the container hook version not set to 5.0 in release 2.312.0 anymore? If so, would you be able to update the release notes as well? I am using the 2.312.0 image and was trying to understand why I couldn't see the new kube-scheduler features reflected (part of the 5.0 hook version release).

[nikola-jokic]

Hey, the hook has this issue, but this PR aims to fix it. Hopefully, we will publish a new hook version soon and maybe re-publish the image (cc @fhammerl)

[github-actions]

This issue does not seem to be a problem with the runner application, it concerns the GitHub actions platform more generally. Could you please post your feedback on the GitHub Community Support Forum which is actively monitored. Using the forum ensures that we route your problem to the correct team. 😃