SDK Manager with Docker

SDKManager is not working properly using the official Docker provided.

We are using a Jetson Xavier NX.

Writing to internal memory for boot was successful. The external memory, in this case the NVME recording is occurring error.

SDK Manager Version
sdkmanager:1.8.3.10409-Ubuntu_18.04

Execution

docker run --rm -it --privileged -v /dev/bus/usb:/dev/bus/usb/ -v /dev:/dev -v /media/$USER:/media/nvidia:slave --name JetPack_NX_Devkit --network host sdkmanager --cli install --logintype devzone --product Jetson --target JETSON_XAVIER_NX_TARGETS --targetos Linux --version 4.6.2 --select ‘Jetson OS’ --deselect ‘Jetson SDK Components’ --flash all --license accept --staylogin true --datacollection enable

Mistake

info: ~/nvidia/nvidia_sdk/JetPack_4.6.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra │
│ ││info: ****************************************** │
│ ││info: * * │
│ ││info: * Step 3: Start the flashing process * │
│ ││info: * * │
│ ││info: ****************************************** │
│ ││info: Waiting for target to boot-up… │
│ ││info: Waiting for target to boot-up… │
│ ││info: Waiting for target to boot-up… │
│ ││info: Waiting for target to boot-up… │
│ ││info: Waiting for target to boot-up… │
│ ││info: Waiting for target to boot-up… │
│ ││info: Waiting for target to boot-up… │
│ ││info: Waiting for target to boot-up…

2 Likes

@asahar, this seems likely to be for you.

Sorry, I couldn’t find exactly what tag to put.

No worries.

Just to understand, can you tell me if the person in charge will respond here or reopen a ticket?

They should answer here. I will ping him again.

1 Like

I’m facing the same issue! Any updates on that?

1 Like

Same problem here.

1 Like

Hi,
Anybody can share the SDK Manager error logs under ~/.nvsdkm folder? We need more details to further understand the issue.
Thanks!

NV_L4T_DRIVERS_T194_COMP.log (1.3 KB)
NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP.log (13.1 KB)
NV_L4T_FLASH_XAVIER_NX_WITH_OS_IMAGE_COMP.log (188.4 KB)

All logs requested.

I forgot to pass another point before, I imagine it has nothing to do with it but it is a pending error in the docker image.

The image is without the “uuid-runtime” package, we are installing it for correct operation.

Please see this

Try adding additional docker arguments

The old “error” has been resolved, however there is still an error at the end.

info: [ 132]: l4t_flash_from_kernel: Flashing success
│info: Error flashing non-qspi storage
│info:
│info: Cleaning up…
│info: [ Component Install Finished with Error ]
│info: [host] [ 9.61 GB used. Disk Avail: 309.46 GB ]
│info: [ NV_L4T_FLASH_XAVIER_NX_WITH_OS_IMAGE_COMP Install took 6m33s ]
│info:
│error: command terminated with error
│info: Installation failed.

The logs are attached.

Note: The --user=0:0 flag needed to be removed, the SdkManager blocks execution as root.

NV_L4T_FLASH_XAVIER_NX_WITH_OS_IMAGE_COMP.log (227.0 KB)
NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP.log (22.3 KB)
NV_L4T_DRIVERS_T194_COMP.log (1.3 KB)

Seems like the docker is missing some binary

Can you install “parted”

Same error after installing “parted”.
NV_L4T_FLASH_XAVIER_NX_WITH_OS_IMAGE_COMP.log (227.2 KB)
NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP.log (21.6 KB)
NV_L4T_DRIVERS_T194_COMP.log (1.3 KB)

Any reason why some packages are missing from the image? is your default docker image.

In your log I saw there is this line

Error: Partition(s) 1 on /dev/sdd have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.

Can you reboot the host and try again?

Flashing to NVMe is a new feature that we have not considered when creating docker container for SDKM; therefore, the docker image is not ready for flashing to NVMe storage. If possible, you can try to install SDKM directly on your host machine for flashing or use something like GitHub - jetsonhacks/rootOnNVMe: Switch the rootfs to a NVMe SSD on the Jetson Xavier NX and Jetson AGX Xavier

After the reboot, it worked correctly. Thanks.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.