Open SkalskiP opened 2 years ago
Hi @SkalskiP, the JetPack 5.0 containers will only run on JetPack 5.x
@dusty-nv follow-up question on this topic, is it possible to only build the images ? We have a jetson on jetpack 4.5 that we use as a CI which builds jetpack 5 images currently and it seems to be working. Should I expect problems ?
We have a jetson on jetpack 4.5 that we use as a CI which builds jetpack 5 images currently and it seems to be working. Should I expect problems ?
I'm not sure, I haven't tried that. Do the images run okay on JetPack 5?
The JetPack 5 images are far more self-contained (in that CUDA/cuDNN/ect are installed inside the container instead of mounted from the host), which is probably why it builds okay on JetPack 4.x
It is still early development, it seems okay for now. I am trying to figure what is still mounted from the host, it seems some libraries for GStreamer might still be mounted somehow. I got an issue where a few libs including /lib/aarch64-linux-gnu/tegra/libdrm.so.2
were empty. It seems to be fixed by adding --runtime nvidia
or --gpus all
It seems to be fixed by adding
--runtime nvidia
or--gpus all
Yes, these will mount those libraries. You can see which ones are mounted by checking the CSV files under /etc/nvidia-container-runtime/host-files-for-container.d/
Awesome this will be really helpful, thanks !
Hello. I'm trying to run
nvcr.io/nvidia/l4t-pytorch:r34.1.0-pth1.12-py3
image on my Jetson AGX Xavier with Jetpack 4.5.1.When I do:
I get:
When I run:
Everything works just fine.