Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Not able to find node12

See original GitHub issue

Describe the bug While Running Runner.client, following error is thrown

OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/__e/linux/amd64/node12/bin/node": stat /__e/linux/amd64/node12/bin/node: no such file or directory: unknown

To Reproduce Steps to reproduce the behavior:

Go to <repo root>
Run ‘Runner.client’
See error

Expected behavior To complete the run successfully

Runner Version and Platform

Version of your runner? 3.2.1

OS of the machine running the runner? OSX/Windows/Linux/… OSX

What’s not working?

OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/__e/linux/amd64/node12/bin/node": stat /__e/linux/amd64/node12/bin/node: no such file or directory: unknown

Job Log Output

log output

Runner and Worker’s Diagnostic Logs

github action

name: CI

on: push

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2

Issue Analytics

State:
Created 2 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

2reactions

ChristopherHXcommented, Aug 6, 2021

I updated the ReadMe to reflect your issue. The official runner blocks docker on macOS runners, therefore this limitation is only relevant for this fork.

Uses in Composite Actions Ready for Experiments 😃 in 3.2.2

1reaction

bhvngtcommented, Jul 29, 2021

I will close this issue. Guess it will be worthwhile to capture that the installation directory needs to be accessible to docker file sharing in readme.

Thank you very much for this great time-saving project.