mdegans/l4t-base repository overview

⁠l4t-base with apt sources

Dockerfiles here⁠.

This image l4t-base with Nvidia's apt sources, so you can build using it without nvidia as the default runtime⁠.

The latest tag is an alias for t210, tx1, and nano. The tag controls the enabled apt repo and nothing else. If you use the --runtime nvidia flag at runtime, many libraries will be mounted over if they exist so this shouldn't matter much, but in some cases having board specific libraries at build time may be useful.

NOTE: on r32.4.3 (latest)

Some (good) changes have been made to the base layer (sudo is gone as the ca-cerificates package), but this breaks apt out of the box. Somewhere in your Dockerfile, or in a script run by the Dockerfile, you must do the following for apt-get update to work:

mv /etc/apt/sources.list.d/nvidia-l4t-apt-source.list /etc/apt/
apt-get update && apt-get install -y --no-install-recommends ca-certificates
mv /etc/apt/nvidia-l4t-apt-source.list /etc/apt/sources.list.d

why? Since ca-certificates is no longer in the base image, but this is required to connect to anything that uses ssl like nvidia's apt repos, the apt list containing nvidia's sources must be temporarily moved out of the way, ca-certificates installed, the list moved back, and the rest of your dependencies installed as usual. Depending on your image's use, you may wish to remove ca-certificates at the end as well, however In any image built off that, you will need to run the above again. It can be a security risk to leave ca-certifacates in the image depending on it's intent. Likewise --allow-unauthenticated is very unsafe to use in this case.

⁠Requirements

• a Tegra board
• Linux for Tegra with Docker running