Is the JetPack 6 build process different, more flexible?

Robotics & Edge Computing Jetson Systems Jetson Xavier NX
1

In a conversation with @prlawrence and my thread with @AastaLLL, they said that JP6 would be more flexible and simpler to do custom integrations with distros.

The JP6 DP page actually says:

For the first time, JetPack 6 brings the flexibility to run any Linux Kernel and offers wider options of Linux based distros from Jetson ecosystem partners

My interest (from that thread) is primarily around the ability to run containers on a different distro, not actually JP6.

Is the process of getting the dependencies to make this work, described in the other thread, different for JP6 than JP5? That process was:

  1. The list of files necessary to be mounted into the container
  2. The process for creating the CDI so that containerd can consume it
  3. The installation of the dependent files (mostly .so libs)

How do I do this for Jp6?

4

Hi,

Is your question for the standard Jetson platform?
JetPack 6 doesn’t support XavierNX. Only Orin series.

Thanks.

5

I didn’t know that. How interesting.

My immediate interest is the XavierNX, but we expect that to expand quickly. So we do want to know the answer to the question.

6

Hi,

Sure, let me discuss this issue with our internal team and update.

Thanks.

7

From the point of view of the NVIDIA Container Toolkit, there are no differences between various JetPack versions. Both platforms provide CSV files (l4t.csv, devices.csv, drivers.csv) that define the entities that are required for containerization. The NVIDIA Container Toolkit consumes these and generates a CDI specification (and if used in the context of the nvidia-container-runtime directly applies this generated specification to an incoming OCI runtime specification).

As pointed out in your other thread, the exercise for supporting a new platform / distribution is then broken down into:

  1. Collecting the required entities (e.g. .so libs)
  2. Constructing (or reusing) the relevant .csv files
  3. Generating the CDI specification from the specified files.

I hope this answers your question somewhat.

8

In other words, for this part, it is unchanged from JP5 to JP6?

9

Yes, for this part I would expect no changes between JP5 and JP6.