sudo docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
<none> <none> fb4900030dde 16 hours ago 6.91GB
nanodb r36.4.2-cudnn_9.4 4d73a710a23c 16 hours ago 6.91GB
nanodb r36.4.2-cuda_12.6 57f6b38b7dd0 16 hours ago 5.91GB
nanodb r36.4.2-build-essential be8f81cd8a0f 16 hours ago 723MB
nanodb r36.4.2-pip_cache_cu126 efca951b50f6 16 hours ago 723MB
ubuntu 22.04 981912c48e9a 3 months ago 69.2MB
dustynv/nanodb r36.2.0 8118ef4e5cab 10 months ago 16GB
From the error log:
e[0mLooking in indexes: http://jetson.webredirect.org/jp5/cu126
e[91mERROR: Could not find a version that satisfies the requirement pip (from versions: none)
e[0me[91mERROR: No matching distribution found for pip
Jetson Orin Nano Super setup:
a) unbox > insert microSD loaded with JetPack 6.1> power-up > fully functional
b) install 500 GB NVMe > install jumper pins 9-10 > connect via USB to Host computer
c) sdkmanager > flash JetPack 6.1 to NVMe success > power-down
d) remove jumper > power-up > boot from NVMe > fully functional including MAXN
e) ollama works
f) start install of NanoDB jetson-containers > build not successful
g) jetson-containers run $(autotag nanodb)…
-- L4T_VERSION=36.4.2 JETPACK_VERSION=5.1 CUDA_VERSION=12.6
-- Finding compatible container image for ['nanodb']
nanodb:r36.4.2-cudnn_9.4
bash: $: command not found
bash: syntax error near unexpected token `packages=['nanodb'],'
h> exit container > sudo apt-cache show nvidia-jetpack
There remains an issue with the r36.4.2 indexing process where the validation step returns a warning for each image being validated:
22:23:21 | INFO | validating index with k=8
22:23:22 | WARNING | incorrect or duplicate index [0] indexes=[-1 -1 -1 -1 -1 -1 -1 -1] distances=[-3.4028235e+38 -3.4028235e+38 -3.4028235e+38 -3.4028235e+38
-3.4028235e+38 -3.4028235e+38 -3.4028235e+38 -3.4028235e+38]
Search queries using this index return an incorrect list of images all with similarity values of 0.0237
IMPORTANT: using the r36.2.0 container pulled from: https://hub.docker.com/r/dustynv/nanodb/tags
results an indexing process that runs 4x faster (than 36.4.2) and generates an index that is validated with few warnings or errors. The index query results are correct.
Not sure if I have correctly built the 36.4.2 container or if the 36.4.2 container has a bug in nanodb per: Nanodb Image Scan Not working
From the logs, the indexing rates of my Jetson Orin Nano Super at MAXN, :
2.5 images per second using container r36.4.2 (elapsed time 28 hours)
10.9 images per second using container r36.2.0 (elapsed time 7 hours)