Sign inSign up

dustynv/l4t-pytorch

By dustynv

•Updated almost 2 years ago

https://github.com/dusty-nv/jetson-containers/packages/l4t/l4t-pytorch

Image
10

100K+

dustynv/l4t-pytorch repository overview

⁠l4t-pytorch

CONTAINERS⁠
CONTAINER IMAGES⁠
Repository/TagDateArchSize
  dustynv/l4t-pytorch:r32.7.1⁠2023-12-14arm641.2GB
  dustynv/l4t-pytorch:r35.2.1⁠2023-12-11arm645.6GB
  dustynv/l4t-pytorch:r35.3.1⁠2023-12-14arm645.6GB
  dustynv/l4t-pytorch:r35.4.1⁠2023-12-12arm645.6GB
  dustynv/l4t-pytorch:r36.2.0⁠2023-12-14arm647.3GB

Container images are compatible with other minor versions of JetPack/L4T:
    • L4T R32.7 containers can run on other versions of L4T R32.7 (JetPack 4.6+)
    • L4T R35.x containers can run on other versions of L4T R35.x (JetPack 5.1+)

RUN CONTAINER⁠

To start the container, you can use jetson-containers run⁠ and autotag⁠, or manually put together a docker run⁠ command:

# automatically pull or build a compatible container image
jetson-containers run $(autotag l4t-pytorch)

# or explicitly specify one of the container images above
jetson-containers run dustynv/l4t-pytorch:r36.2.0

# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host dustynv/l4t-pytorch:r36.2.0

jetson-containers run⁠ forwards arguments to docker run⁠ with some defaults added (like --runtime nvidia, mounts a /data cache, and detects devices)
autotag⁠ finds a container image that's compatible with your version of JetPack/L4T - either locally, pulled from a registry, or by building it.

To mount your own directories into the container, use the -v⁠ or --volume⁠ flags:

jetson-containers run -v /path/on/host:/path/in/container $(autotag l4t-pytorch)

To launch the container running a command, as opposed to an interactive shell:

jetson-containers run $(autotag l4t-pytorch) my_app --abc xyz

You can pass any options to it that you would to docker run⁠, and it'll print out the full command that it constructs before executing it.

BUILD CONTAINER⁠
⁠

If you use ⁠autotag⁠ as shown above, it'll ask to build the container for you if needed. To manually build it, first do the system setup⁠, then run:

jetson-containers build l4t-pytorch

The dependencies from above will be built into the container, and it'll be tested during. Run it with --help⁠ for build options.

Tag summary

Content type

Image

Digest

sha256:46f387eaa…

Size

7.8 GB

Last updated

almost 2 years ago

docker pull dustynv/l4t-pytorch:2.2-r35.4.1