JetPack 6.2 Host with JetPack 5.2 Container — glibc Incompatibility at Runtime

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

Hi,

I’m running into a runtime issue with my setup:

  • Host: JetPack 6.2 (glibc 2.35)
  • Container: JetPack 5.2-based (CUDA 11.8, glibc 2.31)
  • My application requires: CUDA 11.8
  • All builds inside the container succeed, but at runtime I get glibc version incompatibility errors from NVIDIA libraries inside the container. Some of them seem to need glibc >= 2.34.

My question is:

  • Aren’t NVIDIA Jetson containers supposed to be isolated from the host glibc?
  • Why does the host glibc version seem to affect the container runtime?
  • Is it possible to run a JetPack 5.2 container on a JetPack 6.2 host cleanly, or is a matching JetPack version required on both?

Any advice on best practices to run legacy JetPack containers on newer hosts would be appreciated.

Thanks!

3

Hi,

This is not supported.

Some hardware-related driver is mounted from the host directly.
So you will need to use the container that is built with the r36 branch support.

r35 container needs to run on the device flashed with JetPack 5.

Thanks.

4

Thank you for the reply, I am now trying to use jetpack 6.2 on host and jetpack 6.2 container.

5

Hi,

Thanks for the feedback.
Do you meet issues when using the 6.2 container?

Thanks.

6

The issue is not there any more, both the host and the containers matching it is working fine. I am able to see the gpu inside the container as well (nvidia-smi) is working both host and inside container.

thank you :-)