opendronemap

opendronemap

CONTAINERS IMAGES RUN BUILD

OpenDroneMap container (website, GitHub) for Jetson. This uses CUDA for accelerated SIFT feature extraction during image alignment & registration, and during SFM reconstruction.

Example to start the container building maps from a directory of images (like from here in the OpenDroneMap documentation)

jetson-containers run \
  -v /home/user/data:/datasets \
  $(autotag opendronemap) \
    python3 /code/run.py \
      --project-path /datasets project

CONTAINERS

opendronemap
Requires	L4T ['>=35']
Dependencies	build-essential pip_cache:cu122 cuda:12.2 cudnn:8.9 python tensorrt cmake numpy onnx onnxruntime ffmpeg
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 opendronemap)

# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host opendronemap:36.3.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 opendronemap)

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

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

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