mirror of
https://github.com/azaion/gps-denied-onboard.git
synced 2026-06-21 19:11:13 +00:00
Oleksandr Bezdieniezhnykh
58a1678417
Three discoveries from on-Jetson build (image builds clean in ~3m18s after fixes; gtsam-4.3a0, torch 2.4.0+cuda, cv2 4.11.0 all import OK inside container running --runtime=nvidia): 1. dustynv/l4t-pytorch's /etc/pip.conf bakes in a local Jetson mirror (jetson.webredirect.org) that's only reachable from the maintainer LAN. pip's DNS lookup fails everywhere else. Wipe the config and pin --index-url to upstream PyPI. 2. The image ships pip 24.2. The SUT's `gtsam<5.0,>=4.2` constraint matches ONLY gtsam-4.3a0 on PyPI (no stable aarch64 wheels), and pip 24.x rejects pre-releases unless --pre is set. The Colima image lands on the same wheel because its pip 26.x has explicit fallback-to-pre-release logic. Bump pip before installing the SUT to align resolver behavior across both harnesses. 3. Skip the [inference] extra entirely — the base image ships Tegra-tuned torch / torchvision that re-pip would clobber with x86 builds lacking cuDNN/cuBLAS for Orin. Co-authored-by: Cursor <cursoragent@cursor.com>
119 lines
5.6 KiB
Docker
119 lines
5.6 KiB
Docker
# Tier-2 e2e-runner image — Jetson Orin Nano (JetPack 6.x, L4T R36.x).
|
|
#
|
|
# AZ-615: companion image to `tests/e2e/Dockerfile` (Colima/Tier-1 smoke
|
|
# harness) that runs the full Reality Gate — including C3 matcher + C7
|
|
# inference — against a CUDA-capable GPU.
|
|
#
|
|
# Hardware contract (operator-confirmed, 2026-05-17):
|
|
# * Jetson Orin Nano, JetPack 6.2.2+b24, L4T R36.5.0
|
|
# * nvidia-container-toolkit ≥ 1.16
|
|
# * `docker run --runtime=nvidia ... nvidia-smi` returns the GPU
|
|
#
|
|
# Image layout mirrors the Colima Dockerfile (so AC-4 AST scan + bind
|
|
# mounts work the same way):
|
|
# /opt/pyproject.toml
|
|
# /opt/src/gps_denied_onboard/... (SUT package, editable install)
|
|
# /opt/tests/... (bind-mounted from host)
|
|
# /opt/_docs/00_problem/input_data/ (bind-mounted from host)
|
|
#
|
|
# Build context is the repo root (see `docker-compose.test.jetson.yml`
|
|
# → `services.e2e-runner.build.context`).
|
|
#
|
|
# BUILD HOST: this image MUST be built ON the Jetson — cross-building
|
|
# from x86 macOS produces images that miss Tegra-specific shared libs
|
|
# the nvidia-container-runtime later mounts at run time.
|
|
|
|
# ---------------------------------------------------------------------------
|
|
# Base — dustynv/l4t-pytorch ships JetPack runtime + PyTorch wheel for `.cuda()`
|
|
#
|
|
# Tag selection rationale (verified 2026-05-17 against the live registries):
|
|
#
|
|
# - `nvcr.io/nvidia/l4t-base` was deprecated in JetPack 6 (forums:
|
|
# "L4T Base docker image for Jetpack 6.2 (r36.4.3)" / Issue #883 in
|
|
# dusty-nv/jetson-containers). The image no longer publishes r36 tags.
|
|
# - `nvcr.io/nvidia/l4t-pytorch` has NO r36 tags published. The newest
|
|
# official l4t-pytorch tag is r35.2.1-pth2.0-py3 — too old for our
|
|
# torch >= 2.2 floor in pyproject.toml `[inference]`.
|
|
# - `nvcr.io/nvidia/l4t-jetpack:r36.4.0` exists (CUDA + cuDNN + TensorRT
|
|
# bundled) but ships NO PyTorch — we'd have to install the Jetson
|
|
# PyTorch wheel from developer.download.nvidia.com manually.
|
|
# - `dustynv/l4t-pytorch:r36.4.0` (Docker Hub) is the de-facto Jetson
|
|
# PyTorch image: maintained by dusty-nv (NVIDIA's Jetson containers
|
|
# maintainer), bakes torch / torchvision / opencv / ONNX runtime for
|
|
# JetPack 6, ARM64, ~6.3 GB. Forward-compatible with the host's
|
|
# slightly newer R36.5 BSP (NVIDIA containers tolerate one minor BSP
|
|
# ahead on the host side).
|
|
#
|
|
# Verify availability before build:
|
|
# docker pull dustynv/l4t-pytorch:r36.4.0
|
|
FROM dustynv/l4t-pytorch:r36.4.0 AS runtime
|
|
|
|
ARG DEBIAN_FRONTEND=noninteractive
|
|
# System deps mirror tests/e2e/Dockerfile + the Jetson runtime stack:
|
|
# * build-essential / libpq-dev / libspatialindex-dev — same as Colima
|
|
# * python3-pip / python3-venv — l4t-pytorch ships python but not always venv
|
|
# * libgl1 + libglib2.0-0 — OpenCV runtime libs (same reason as Colima)
|
|
# * libpq5 + libspatialindex-c6 — runtime side of psycopg + rtree
|
|
# Note: CUDA / cuDNN / TensorRT come pre-baked in the base image — do NOT
|
|
# attempt to apt-install them (would conflict with the Tegra-specific libs
|
|
# the runtime mounts).
|
|
RUN apt-get update && apt-get install -y --no-install-recommends \
|
|
ca-certificates \
|
|
build-essential \
|
|
libpq-dev \
|
|
libspatialindex-dev \
|
|
libpq5 \
|
|
libspatialindex-c6 \
|
|
libgl1 \
|
|
libglib2.0-0 \
|
|
python3-pip \
|
|
python3-venv \
|
|
&& rm -rf /var/lib/apt/lists/*
|
|
|
|
WORKDIR /opt
|
|
|
|
# Editable SUT install. Skipping the `[inference]` extra because PyTorch +
|
|
# torchvision are already provided by the l4t-pytorch base image with
|
|
# Tegra-specific CUDA builds; reinstalling them from PyPI would clobber
|
|
# the Tegra wheels with x86-compatible ones that lack the cuDNN / cuBLAS
|
|
# linkage required by Orin.
|
|
COPY pyproject.toml README.md ./
|
|
COPY src ./src
|
|
|
|
# `--break-system-packages` is needed because the l4t-pytorch base image
|
|
# uses an externally-managed Python environment (PEP 668). The alternative
|
|
# would be to layer a venv on top of the pre-installed torch, but that
|
|
# would shadow the Tegra-tuned torch wheel and break `.cuda()`. The image
|
|
# IS the environment; embracing system-pip is the path of least drift.
|
|
#
|
|
# The dustynv base bakes two stale indexes into /etc/pip.conf:
|
|
# * http://jetson.webredirect.org/jp6/cu126 — a local mirror only
|
|
# reachable from the maintainer's LAN; DNS-fails everywhere else.
|
|
# * https://pypi.ngc.nvidia.com — NVIDIA NGC; doesn't have most
|
|
# standard packages like setuptools>=68.
|
|
# Both are intended for installing Tegra-tuned PyTorch wheels, which
|
|
# we don't need to do — they're already in the base image. Wipe the
|
|
# bake'd config and pin to upstream PyPI for the dev extras only.
|
|
RUN rm -f /etc/pip.conf /root/.pip/pip.conf /root/.config/pip/pip.conf
|
|
|
|
# Bump pip from 24.2 → latest. 24.2 rejects pre-release versions for
|
|
# specifiers like `gtsam<5.0,>=4.2` even when 4.3a0 is the only wheel
|
|
# PyPI ships for aarch64 (the Colima image lands on the same gtsam
|
|
# 4.3a0 because its pip 26.x has explicit "fallback to pre-release
|
|
# when no stable candidates match" logic). Keeping pip current also
|
|
# avoids future drift between the two harnesses.
|
|
RUN pip3 install --no-cache-dir --break-system-packages \
|
|
--index-url https://pypi.org/simple \
|
|
--upgrade pip
|
|
|
|
RUN pip3 install --no-cache-dir --break-system-packages \
|
|
--index-url https://pypi.org/simple \
|
|
-e ".[dev]"
|
|
|
|
# ENTRYPOINT mirrors the Colima Dockerfile — pytest discovers both
|
|
# `tests/e2e/replay/` (heavy tier2 ACs run with GPS_DENIED_TIER=2) and
|
|
# any future `tests/e2e/scenarios/` additions. Rootdir resolves to /opt
|
|
# via the COPY'd pyproject.toml so `from tests.e2e.replay._helpers import ...`
|
|
# works inside the test files.
|
|
ENTRYPOINT ["pytest", "-q", "/opt/tests/e2e/"]
|