Software IntegrationDocker

Creating a Docker Image for your ZED Application

Open in ClaudeOpen in ChatGPT

This is the recommended workflow for creating your own Docker image for your application:

  1. Write a Dockerfile for your application.
  2. Build the image with docker build command.
  3. Host your Docker image on a registry.
  4. Pull and run the image on the target machine.

Write the Dockerfile

Docker builds images automatically by reading the instructions from a Dockerfile. It is a text file that contains all commands needed to build a given image.

In the following example, we will build and run the Hello ZED tutorial application in a container.

First let’s prepare the host with the code:

$git clone https://github.com/stereolabs/zed-sdk.git
$cd zed-examples/tutorials/tutorial\ 1\ -\ hello\ ZED/

Open a text editor and create a new Dockerfile with the following content:

1# Specify the parent image from which we build
2FROM stereolabs/zed:3.7-gl-devel-cuda11.4-ubuntu20.04
3
4# Set the working directory
5WORKDIR /app
6
7# Copy files from your host to your current working directory
8COPY cpp hello_zed_src
9
10# Build the application with cmake
11RUN mkdir /app/hello_zed_src/build && cd /app/hello_zed_src/build && \
12    cmake -DCMAKE_LIBRARY_PATH=/usr/local/cuda/lib64/stubs \
13      -DCMAKE_CXX_FLAGS="-Wl,--allow-shlib-undefined" .. && \
14    make
15
16# Run the application
17CMD ["/app/hello_zed_src/build/ZED_Tutorial_1"]

We provide some extra arguments to CMake to ensure that CMake and GCC can find all the required CUDA libraries. We also tell the compiler to allow linking even if there are undefined symbols from libraries such as nvcuvid that are not yet available. These will be available at runtime by using the NVIDIA® container toolkit.

For more information on writing dockerfiles, check Dockerfile reference documentation.

Build your Docker Image

Now that you have created a Dockerfile, it’s time to build your image using the docker build command.

$docker build -t hellozed:v1 .

Tips: On NVIDIA® Jetson™, we recommend building your Jetson™ Docker Container on x86 host, and running it on the target NVIDIA® Jetson™ device to avoid long compilation time on boards such as NVIDIA® Jetson™ Nano.

Test the Image

Let’s start the container based on the new image we created using the docker run command.

$docker run -it --gpus all -e NVIDIA_DRIVER_CAPABILITIES=all --privileged -v /dev:/dev hellozed:v1

On NVIDIA® Jetson™ or older Docker versions, use these arguments:

$docker run -it --runtime nvidia --privileged -v /dev:/dev hellozed:v1

If you use ZED X, you need a few more shared volumes.

$docker run -it --runtime nvidia --privileged -v /dev:/dev -v /tmp:/tmp -v /etc/systemd/system/zed_x_daemon.service:/etc/systemd/system/zed_x_daemon.service -v /var/nvidia/nvcam/settings/:/var/nvidia/nvcam/settings/ hellozed:v1

You should now see the output of the terminal.

$docker run -it --gpus all --privileged hellozed:v1
$    Hello! This is my serial number: 23468248

When running a Docker image on an NVIDIA® Jetson™ device, please ensure that the L4T (Linux for Tegra) version of your host system matches the L4T version of the container you are using.

Volumes

When running a Docker image for ZED Cameras a few volumes should be shared with the host.

  • [optional] /usr/local/zed/resources:/usr/local/zed/resources: if you plan to use the AI module of the ZED SDK (Object Detection, Skeleton Tracking, NEURAL depth) we suggest binding mounting a folder to avoid downloading and optimizing the AI models each time the Docker image is restarted. The first time you use the AI model inside the Docker image, it will be downloaded and optimized in the local bound-mounted folder, and stored there for the next runs.
  • [required] /dev:/dev: required to share the video devices
  • For GMSL2 cameras (ZED X):
    • [required] /tmp:/tmp
    • [required] /var/nvidia/nvcam/settings/:/var/nvidia/nvcam/settings/
    • [required] /etc/systemd/system/zed_x_daemon.service:/etc/systemd/system/zed_x_daemon.service

Optimize your Image Size

Docker images can get very large and become a problem when pulling over the network or pushing on devices with limited storage (such as NVIDIA® Jetson™ Nano). Here is a few pieces of advice to keep your image size small:

  • Minimize the number of RUN commands. Each command adds a layer to the image, so consolidating the number of RUN can reduce the number of layers in the final image. Note that layers are designed to be reusable, and will not be pushed or pulled if they didn’t change.

  • Use --no-install-recommends when installing packages with apt-get install to disable the installation of optional packages and save disk space.

  • Remove tarballs or other archive files that were copied during the installation. Each layer is added on top of the others, so files that were not removed in a given RUN step will be present in the final image even if they are removed in a later RUN step.

  • Similarly, clean package lists that are downloaded with apt-get update by removing /var/lib/apt/lists/* in the same RUN step.

  • Create separate images for development and production. Production images should not include all of the libraries and dependencies pulled in by the build.

  • Use multi-stage builds (see Docker docs) and push only your prod image.

$RUN apt-get update -y && \
>    apt-get autoremove -y && \
>    apt-get install --no-install-recommends lsb-release && \
>    tar -xvf archive.tar.gz &&\
>    rm -rf /var/lib/apt/lists/* && \
>    rm -rf archive.tar.gz

Host your Docker Image

Now that you have created your image, you need to share it on a registry so it can be downloaded and run on any destination machine. A registry is a stateless, server-side application that stores and lets you distribute Docker images.

Use Docker Hub Registry

By default, Docker provides an official free-to-use registry, DockerHub, where you can push and pull your images. For example at StereoLabs, the ZED SDK Docker images are built automatically by a public Gitlab CI job and pushed to StereoLabs DockerHub repository.

There are situations where you will not want your image to be publicly available. In this case, you need to create your own private Docker Registry. You can get private repos from Docker, or from many other third-party providers.

Use Local Registry Server

For local development, if your host and target machines are on the same network, you can set up a local registry server and push your images there.

For more information on deploying your own registry server, please refer to Docker docs.

Save and Load Images as Files

Lastly it is also possible to export and load your Docker image as a file.

To export a Docker image simply use :

$# Saving can take some time depending on the image size
$docker save hellozed:v1 -o hellozed_v1.tar

On the destination machine, simply load the Docker image using :

$docker load -i hellozed_v1.tar
$
$cc967c529ced: Loading layer [==================================================>]  65.57MB/65.57MB
$2c6ac8e5063e: Loading layer [==================================================>]  991.2kB/991.2kB
$6c01b5a53aac: Loading layer [==================================================>]  15.87kB/15.87kB
$e0b3afb09dc3: Loading layer [==================================================>]  3.072kB/3.072kB
$37b9a4b22186: Loading layer [==================================================>]   17.1MB/17.1MB
$dd841c774a30: Loading layer [==================================================>]  29.22MB/29.22MB
$52ad947270f1: Loading layer [==================================================>]  3.072kB/3.072kB
$4e3516398cef: Loading layer [==================================================>]  793.6MB/793.6MB
$582ab80c9f26: Loading layer [==================================================>]  1.394GB/1.394GB
$85fd2f8b4dc8: Loading layer [==================================================>]  3.727GB/3.727GB
$d5bd3dceedb5: Loading layer [==================================================>]  222.1MB/222.1MB
$f6b7ec875383: Loading layer [==================================================>]  2.048kB/2.048kB
$eef68a3e44c4: Loading layer [==================================================>]  11.78kB/11.78kB
$2b29f57c8c23: Loading layer [==================================================>]  930.3kB/930.3kB
$Loaded image: hellozed:v1