Hello, we are having issues with our Jetson Nano. We are going through the steps and got to step “Running” (Running VMC Software | Bell AVR Documentation)
where we encountered our first road block. If someone could please help us with this matter it would be greatly appreciated!
root@bellvrc2-desktop:/home/bellvrc2/AVR-2022/VMC# ./start.py run
Running command: docker-compose --project-name AVR-2022 --file /tmp/docker-compose-o11bv0ss.yml up --remove-orphans --force-recreate mavp2p status apriltag thermal mqtt pcm vio fcm fusion
/snap/docker/2281/lib/python3.6/site-packages/paramiko/transport.py:33: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography and will be removed in a future release.
from cryptography.hazmat.backends import default_backend
ERROR: .FileNotFoundError: [Errno 2] No such file or directory: ‘/tmp/docker-compose-o11bv0ss.yml’
When looking in the directory of the “missing file” we saw that the file wasn’t missing.
After attempting the command “sudo service docker start” and reattempting our command “./start.py run” . We still received the same error. The only difference was the file name. When running the command the Jetson will create the docker-compose-********.yml file in the /tmp directory. With the “*” being changed every time you attempt the command.
The different file name is expected, my script creates a temp file every time, based on the launch options you gave it (it’s currently not smart enough to re-use existing files).
As you said, the file is there, the script never deletes it, so I still think there’s some problem with Docker.
What do you get as output when you run sudo service docker status? Not a Jetson, but mine looks like this:
Another thing to look at would be the logs from the Docker service. This can be viewed with: sudo journalctl -u docker -b -e. That command will jump you right to the end too, of the current boot of the Docker service (remove -b to look at ALL previous boots).
I’d like to see what that says before you try anything, but my next steps would be to reinstall Docker, or flash the Jetson fresh from the Nvidia official image. Reinstalling Docker is pretty quick, but it may not successful with all the special sauce Nvidia adds.
As for help at the competition, I really don’t know, sorry. I live in Iowa, so will not be in attendance, and from what I know the Bell team has been extremely short staffed lately.