Jetpack 6.0 Installation Failure Using SDK Manager with docker and wsl

Hi! I’m Subeen Jeong.

I’m trying to install SDK and flash my AGX Orin Development kit 64gb.
I use WSL2 Ubuntu20.04 on Windows11.
I tried installing jetpack 6.0 using both docker image and debian file.

Both docker image and wsl-ubuntu are Ubuntu-20.04, using sdkmanager-cli for docker and sdkmanager-gui for debian installation file.

Both options are seems like successful up to installation for host pc and target, fail in flashing Jetson.
(See photo)

Docker

I run :

 docker run -it --rm sdkmanager --query interactive 

then :

docker run -it --rm sdkmanager --cli --action install --login-type devzone --product Jetson --target-os Linux --version 6.0 --host --target JETSON_AGX_ORIN_TARGETS --select HOST --select 'Jetson Linux' --select 'Jetson Linux image' --select 'Flash Jetson Linux' --select 'Jetson Runtime Components' --select 'Additional Setups' --select 'CUDA Runtime' --select 'NVIDIA Container Runtime' --deselect 'CUDA X-AI Runtime' --deselect 'Computer Vision Runtime' --deselect Multimedia --deselect 'Jetson SDK Components' --deselect CUDA --deselect 'CUDA-X AI' --deselect 'Computer Vision' --deselect 'Developer Tools' --deselect 'Jetson Platform Services' --deselect 'Jetson Platform Services' --flash

It looked like it was installed as shown in the picture below, but at the log file, there is a history of failure from download.


What does the timeout of terminal log mean?

My host pc has been online, and USB-c connection with Jetson have not been disconnected. I checked it through the ‘lsusb’ command, and I also did bind and attach from host pc’s windows using usbipd.

When using the superuser command, it ends with a guide that says it cannot be installed in sudo state.

Debian file

In the GUI state, it seemed to succeed by entering wsl’s sudo password, and even entered jetson’s username and password.
However, after entering username and password, the program stopped after the instruction that jetson was removed.

It has not progressed over time in the state below.



image

Hi,
Please follow the steps in

Windows Subsystem for Linux (WSL) — SDK Manager 2.1.0 documentation

It seems like you run docker on WSL. This environment may not work properly. Suggest directly execute the steps on WSL.