README.md

docker

CONTAINERS IMAGES RUN BUILD

This container has the Docker CLI tools installed in it, and can perform Docker operations (such as starting/stopping containers) through the host's Docker daemon. Access to the host's Docker daemon should be mounted with --volume /var/run/docker.sock:/var/run/docker.sock (which is automatically done by jetson-containers/run.sh). Then it will share all the same container images and instances that are available on the host.

This is not technically Docker-in-Docker, as the container is not running its own Docker daemon (but rather sharing the host's). For more info, see Jérôme Petazzoni's excellent blog post on the subject, which outlines the pro's and con's and common pitfalls of these approaches. In particular, mounting the Docker socket as mentioned above allieviates many of these issues and does not require the --privileged flag.

This approach works with --runtime nvidia and access to the GPU. Note that if you're starting a container within this container and trying to mount volumes, the paths are referenced from the host (see https://stackoverflow.com/a/31381323)

CONTAINERS

docker
Requires	L4T ['>=32.6']
Dependencies	build-essential python
Dependants	l4t-text-generation
Dockerfile	Dockerfile

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 docker)

# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host docker:35.2.1

^{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 docker)

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

jetson-containers run $(autotag docker) 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 docker

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