executable file not found error
See original GitHub issueI see this error when a user logs in and spawns their server on Jupyterhub:
[Warning] Exec lifecycle hook ([gitpuller https://github.com/mcveanlab/tskit-workshop.git master tskit-workshop]) for Container "notebook" in Pod
"jupyter-geoff4_jhub(3f96c04d-fed4-11e8-833f-fa163ec7319d)" failed -
error: command 'gitpuller https://github.com/mcveanlab/tskit-workshop.git master tskit-workshop' exited with 126: , message: "OCI runtime exec failed: exec failed: container_linux.go:348:
starting container process caused \"exec: \\\"gitpuller\\\": executable file not found in $PATH\": unknown\r\n"
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (7 by maintainers)
Top Results From Across the Web
docker: executable file not found in $PATH - Stack Overflow
In the error message shown: Error response from daemon: Cannot start container foo_1: \ exec: "grunt serve": executable file not found in $PATH....
Read more >How to fix docker error executable file not found in $PATH?
Make sure the script my-custom-script.sh is available - the First check which you should perform is by checking the shell script my-custom- ...
Read more >executable file not found in $PATH · Issue #3597 - GitHub
executable file not found in $PATH error message is displayed although the executable is in path. Only containerd 1.2.8 version is affected.
Read more >Executable file not found in %PATH% - Infrastructure
I have confirmed the path to powershell.exe is indeed in the SYSTEM path and powershell scripts and command works everywhere else except for...
Read more >docker executable file not found in PATH | Edureka Community
This error can occur when your executable file do not have the execute permission. chmod +x docker-entrypoint.sh. This might help.
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
Closing, because this was solved by explicitly setting the tag on the image and then referring to that in the Jupyterhub configuration. Thanks to @consideRatio for the help.
@verdurin Ah I’m glad, thanks for following up!