OCI runtime exec failed: exec failed: container_linux.go:349
togoenvogue opened this issue · comments
Hello,
I have been trying since to use the console on my live instances, but none worked.
I even copied and paste the example in the documentation, but it didn't work.
openode exec ls -la
OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: "openode": executable file not found in $PATH": unknown STDERR:
command terminated with exit code 126
Could somebody help?
Thank you
The issue "openode": executable file not found" seems to mean that the package openode is not available in your PATH.
If you are using the UI (in the administration), note that openode is not by default available.
Also note that:
openode exec ls -la
Please use with quotes, openode exec "ls -la"