Dusty-nv/jetson-containers

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Good day ,

Trying to run a sample docker container (dusty-nv) , but really struggling with permission issues …

Command/error:

root@ubuntu:/media/kopbeen/steek2_0/jetson-containers/dusty-nv/jetson-containers# ./build.sh
bash: ./build.sh: Permission denied

bash: /root/bin/autotag: Permission denied
bash: /usr/local/bin/jetson-containers: Permission denied
root@ubuntu:/usr/local/bin#
root@ubuntu:/usr/local/bin#
root@ubuntu:/usr/local/bin# chmod 755 /
chmod 755 /bin
chmod 755 /lib

Tried various chmod commands to try set the permissions, but not getting any joy:

  • chmod +wrx build.sh

root@ubuntu:/usr/local/bin# docker version
Client: Docker Engine - Community
Version: 28.5.1
API version: 1.51
Go version: go1.24.8
Git commit: e180ab8
Built: Wed Oct 8 12:18:14 2025
OS/Arch: linux/arm64
Context: default

Server: Docker Engine - Community
Engine:
Version: 28.5.1
API version: 1.51 (minimum version 1.24)
Go version: go1.24.8
Git commit: f8215cc
Built: Wed Oct 8 12:18:14 2025
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: v1.7.28
GitCommit: b98a3aace656320842a23f4a392a33f46af97866
nvidia:
Version: 1.3.0
GitCommit: v1.3.0-0-g4ca628d1
docker-init:
Version: 0.19.0
GitCommit: de40ad0

5

Hi,

Could you share the output of the command below:

$ ll /media/kopbeen/steek2_0/jetson-containers/dusty-nv/*

Thanks.

6

Hi, sure thing !

root@ubuntu:/media/kopbeen/steek2_0/jetson-containers/dusty-nv# ll *
total 896
drwxr-xr-x 11 kopbeen kopbeen 32768 Nov 5 12:06 ./
drwxr-xr-x 3 kopbeen kopbeen 32768 Nov 5 12:00 ../
-rw-r–r-- 1 kopbeen kopbeen 1672 Nov 5 12:01 autotag
-rw-r–r-- 1 kopbeen kopbeen 364 Nov 5 12:01 build.sh
-rw-r–r-- 1 kopbeen kopbeen 469 Nov 5 12:01 CITATION.cff
drwxr-xr-x 13 kopbeen kopbeen 32768 Nov 5 12:01 data/
drwxr-xr-x 10 kopbeen kopbeen 32768 Nov 5 12:01 deprecated/
-rw-r–r-- 1 kopbeen kopbeen 3015 Nov 5 12:02 docker-compose.yaml
-rw-r–r-- 1 kopbeen kopbeen 36 Nov 5 12:01 .dockerignore
drwxr-xr-x 2 kopbeen kopbeen 32768 Nov 5 12:02 docs/
-rw-r–r-- 1 kopbeen kopbeen 688 Nov 5 12:01 .editorconfig
-rw-r–r-- 1 kopbeen kopbeen 2187 Nov 5 12:06 .env
-rw-r–r-- 1 kopbeen kopbeen 2187 Nov 5 12:01 .env.default
drwxr-xr-x 8 kopbeen kopbeen 32768 Nov 5 12:05 .git/
drwxr-xr-x 4 kopbeen kopbeen 32768 Nov 5 12:01 .github/
-rw-r–r-- 1 kopbeen kopbeen 231 Nov 5 12:01 .gitignore
-rw-r–r-- 1 kopbeen kopbeen 5076 Nov 5 12:02 install.sh
-rw-r–r-- 1 kopbeen kopbeen 1326 Nov 5 12:02 jetson-containers
drwxr-xr-x 2 kopbeen kopbeen 32768 Nov 5 12:02 jetson_containers/
-rw-r–r-- 1 kopbeen kopbeen 1147 Nov 5 12:01 LICENSE.md
drwxr-xr-x 25 kopbeen kopbeen 32768 Nov 5 12:05 packages/
-rw-r–r-- 1 kopbeen kopbeen 1359 Nov 5 12:01 .pre-commit-config.yaml
-rw-r–r-- 1 kopbeen kopbeen 319 Nov 5 12:05 pyproject.toml
-rw-r–r-- 1 kopbeen kopbeen 19638 Nov 5 12:01 README.md
-rw-r–r-- 1 kopbeen kopbeen 156 Nov 5 12:05 requirements.txt
-rw-r–r-- 1 kopbeen kopbeen 13218 Nov 5 12:05 run.sh
drwxr-xr-x 2 kopbeen kopbeen 32768 Nov 5 12:05 scripts/
drwxr-xr-x 2 kopbeen kopbeen 32768 Nov 5 12:05 test_suite/

```Preformatted text
7

Your build.sh lacks execute permissions:
-rw-r–r-- 1 kopbeen kopbeen 364 Nov 5 12:01 build.sh

You can either use chmod to make it executable by you, or you can use it as data:
bash ./build.sh

If you’re going to work on this over time it is easier to change permissions, e.g.:
chmod g+x build.sh
(you own the file, so it shouldn’t require root/sudo)

8

Hi , here is the output of that command:

oot@jetson-host:/media/kopbeen/steek2_0/dusty-nv/jetson-containers# bash ./build.sh

[Warn] Unknown L4T_VERSION: 36.4.7

Namespace(packages=, name=‘’, base=‘’, multiple=False, build_flags=‘’, build_args=‘’, use_proxy=False, package_dirs=[‘’], list_packages=False, show_packages=False, skip_packages=[‘’], skip_errors=False, skip_tests=[‘’], test_only=[‘’], simulate=False, push=‘’, no_github_api=False, log_dir=None, log_level=None, log_colors=None, log_status=None, debug=False, verbose=False, version=False)

┌───────────────────────┬────────────────────────┐
│ L4T_VERSION 36.4.7 │ JETPACK_VERSION 6.2 │
│ CUDA_VERSION 12.6 │ PYTHON_VERSION 3.10 │
│ SYSTEM_ARCH aarch64 │ LSB_RELEASE 22.04 │
└───────────────────────┴────────────────────────┘

$ jetson-containers

[14:42:14] =====================================================================================
[14:42:14] =====================================================================================
[14:42:14] 💣 jetson-containers build failed after 0.0 seconds (0.0 minutes)
[14:42:14] Error: must specify at least one package to build
[14:42:14] =====================================================================================
[14:42:14] =====================================================================================
[14:42:14] Failed building:

Traceback (most recent call last):
File “/media/kopbeen/steek2_0/dusty-nv/jetson-containers/jetson_containers/build.py”, line 136, in
build_container(**vars(args))
File “/media/kopbeen/steek2_0/dusty-nv/jetson-containers/jetson_containers/container.py”, line 106, in build_container
raise ValueError(“must specify at least one package to build”)
ValueError: must specify at least one package to build

9

I’m not familiar with the actual software the build.sh is working with, but apparently it doesn’t like the L4T R36.4.7 release. Maybe it just needs an argument passed? Don’t know since I’m not familiar with the specific software.

10

Hi,

It looks like you git clone with kopbeen but try to execute it with root.
Could you share the use case for trying this?
Or could you clone with the same user account and try it again?

Thanks.

11

Hi thanks - will try to clone and execute with the ‘kopbeen’ user account – thank you .