Document the minimum dependencies necessary to use this action with custom containers
See original GitHub issueIt would be nice to know the minimum amount of software necessary to run this with a custom container. For example, this project requires git
at at least v2.18.
I’m currently trying to debug this failure:
/usr/bin/docker exec 186a95cc5746a0d66133af0ae7ec9e161d903825e4c12bdf02f1a2fcede1fe14 sh -c "cat /etc/*release | grep ^ID"
Running JavaScript Action with default external tool: node12
OCI runtime exec failed: exec failed: container_linux.go:346: starting container process caused "no such file or directory": unknown
I suspect this means I need to add Node.js to the container image but I’m not sure.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Use custom containers in Dataflow
A custom SDK container image must meet the following requirements: The Apache Beam SDK and necessary dependencies are installed.
Read more >Document docker poetry best practices #1879
I'm assuming you start the dev container with the bind mount active and then run poetry install (for the first time or at...
Read more >Custom containers overview | Vertex AI
Custom containers let you specify and pre-install all the dependencies needed for your application. Faster start-up time. If you use a custom container...
Read more >Control startup and shutdown order in Compose
Compose always starts and stops containers in dependency order, where dependencies are determined by depends_on , links , volumes_from , and network_mode: ...
Read more >Image-building best practices
Update the Dockerfile to copy in the package.json first, install dependencies, and then copy everything else in. · Create a file named ....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m still seeing this with actions/checkout@v2 and also
master
. I’m running on self-hosted runner, with a custom container:Since this issue is related to actions/checkout, but we use this issue board to track issues with the runner, I am closing this issue.