dusty-nv
commented
1 year ago Hi @usaotearoa, please see my reply to your forum post here:
Open usaotearoa opened 1 year ago
dusty-nv
commented
1 year ago Hi @usaotearoa, please see my reply to your forum post here:
Hi Dusty!
First of all, thank you for all the efforts you put into building these containers, the easy-to-follow tutorials, and all the community engagement you do! I'm really grateful for such a good source of information.
For weeks now, I have been struggling to get the Jetson Nano Developer Kit (4GB, B01 with 2 MIPI-ports) to work properly. I'm trying to get a docker container with ROS2 running. Ideally that would be Humble, but I guess I will have to get by with Foxy, as Galactic is EOL.
This has been tried on multiple Jetson Nano Developer Kits, as I have two of them. Here are the steps outlined of what has been done:
REGULAR DOCKER IMAGE WORKFLOW Flash the device with the latest sdkmanager to JetPack 4.6.3. (I have also tried flashing it to 32.7.1, but the steps below still fail. If I opt for DeepStream or not also does not change the outcome.)
After the device is finished, log in and run apt-get update && upgrade (In some trials, this step was omitted and yet the following procedure still failed.) Clone the GitHub repository (git clone https://github.com/dusty-nv/jetson-containers.git) Ensure "default-runtime": "nvidia" is entered in the /etc/docker/daemon.json, properly formatted and comma added after the prior entry! Then run one of the following scripts:
This fails because I'm already on 32.7.3.
Modified the l4t_version.sh to fake the output to show R32.7.1 (Even if this step is not needed due to being on Jetpack 4.6.1 and R32.7.1, as mentioned above, the process fails)
Then attempt to run the docker command from step 5 again, and it actually works, loading the docker. Following the tutorial for microROS for Teensy
(https://micro.ros.org/docs/tutorials/core/teensy_with_arduino/),the process fails at the following step:Also, the very first source command to source the environment is wrong. It is:
But it should be:
source /opt/ros/foxy/install/setup.bash
However, despite this small oversight, the agent build still fails.
I know this is not related to the Jetpack version, as mentioned it fails with 4.6.1 as well. At some point, I was able to get it working, but I'm unsure what I have done differently and why it suddenly wouldn't work anymore. Output logs are to follow below. BUILD DOCKER IMAGE WORKFLOW
Then I decided to build the docker container from source, as I thought maybe there is something intrinsically different in my system, and building from source will sort all dependencies properly. This has been tried under the following circumstances:
No matter what I attempt to do, the build process also fails.
So to summarize, my situation is as follows:
Output logs are to follow below.
Thank you for your time!
Here the entire output from an attempt on a freshly flashed Jetson Nano with Jetpack 4.6.1 (R32.7.1). entire trace below: Because I have done this process so many times and am getting tired of typing / copying and pasting all commands, I have thrown them into a shell script. But if I do it manually of with the script, the outcome is the same. Here the script:
And here the terminal trace from executing the script:
I'm so desperate for a solution and actually have chatted with chatGPT :-/ which suggested to:
Which I have done prior to running the script, but to little success, as above shows :-/
Would you kindly advice?