Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

starting container process caused "exec: \"python\": executable file not found in $PATH" #62

Open
oscar-o-oneill opened this issue Oct 3, 2020 · 4 comments
Assignees

Comments

@oscar-o-oneill
Copy link

Issue:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"python\": executable file not found in $PATH": unknown. ERRO[0006] error waiting for container: context canceled

I am trying to get the linux CV server going on my Azure GPU VM on Ubuntu 16.04 LTS. The VM is NC6_Promo with 6 vCPUs, 56GB of RAM and 128GB SSD.

I ran the install script on a newly created VM and everything seemed to install OK. nvidia-smi shows the correct output and the GPU is working.

I ran docker run -p 8501:80 -e NVIDIA_VISIBLE_DEVICES="0" controls_detection eula=accept but this does not work and results in the error message at the very top of this issue. It appears to be some kind of python environment issue. Possibly in the docker container.

Any ideas on how to fix this? I may try to use RHEL instead of Ubuntu to see if that makes a difference.

Thanks!

@ubikusss
Copy link
Contributor

ubikusss commented Feb 3, 2021

I am sorry for the late response here. Is this issue resolved or does it require additional investigation?

@oscar-o-oneill
Copy link
Author

I never resolved this issue with the CV Server on Ubuntu 16.04 LTS. I did try the CV Server on RHEL as well, but that did not work either. But I did get the CV Server working on Windows.

@OodapowUiPath
Copy link

@oscar-o-oneill when was the controls_detection.tar downloaded? Maybe a new one would do the trick. I tested the tar that is currently in production, and it seems to work. I can try reproducing the bug with your tar if you could share it.

@oscar-o-oneill
Copy link
Author

@oscar-o-oneill when was the controls_detection.tar downloaded? Maybe a new one would do the trick. I tested the tar that is currently in production, and it seems to work. I can try reproducing the bug with your tar if you could share it.

Hi, I downloaded the controls_detection.tar around the same time as this original post, so maybe around September or October 2020. I haven't tried it with a newer container package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants