Metropolis Microservices for Jetson

[sarodeanil35]

I have started with Metropolis Microservices for Jetson and wanted to install the application bundle on Jetson AGX Orin, I am following the following Part 2: Hardware and Software Installation of AI-NVR | NVIDIA On-Demand and the following are the my hardware and software stacks.

Hardware: Jetson AGX Orin.

Software:

Jetpack: Version: 6.0-b52
deepstream-app version 6.4.0
DeepStreamSDK 6.4.0

While following the above video, I did not understand why we had to use the below command

sudo apt-key adv --fetch-keys http://l4t-repo.nvidia.com/jetosn-ota-internal.key

and further adding below two lines in the nvidia@ubuntu:/etc/apt/sources.list.d$ sudo nano nvidia-l4t-apt-source.list

deb http://l4t-repo.nvidia.com/common r36.2 main
deb http://l4t-repo.nvidia.com/t234 r36.2 main

when I did sudo apt update, I got the following errors

nvidia@ubuntu:/etc/apt/sources.list.d$ sudo apt update
Hit:1 https://download.docker.com/linux/ubuntu jammy InRelease
Hit:2 https://repo.download.nvidia.com/jetson/common r36.2 InRelease                                                                                             
Hit:3 https://repo.download.nvidia.com/jetson/t234 r36.2 InRelease                                                            
Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy InRelease                  
Get:5 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease [119 kB]
Get:6 http://l4t-repo.nvidia.com/common r36.2 InRelease [2,561 B]
Hit:7 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease  
Get:8 http://l4t-repo.nvidia.com/t234 r36.2 InRelease [2,558 B]
Err:6 http://l4t-repo.nvidia.com/common r36.2 InRelease    
The following signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 6E3279734C41A135
Get:9 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [110 kB]
Err:8 http://l4t-repo.nvidia.com/t234 r36.2 InRelease
The following signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 6E3279734C41A135
Reading package lists... Done
W: GPG error: http://l4t-repo.nvidia.com/common r36.2 InRelease: The following 
signatures couldn't be verified because the public key is not available: NO_PUBKEY 6E3279734C41A135
E: The repository 'http://l4t-repo.nvidia.com/common r36.2 InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://l4t-repo.nvidia.com/t234 r36.2 InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6E3279734C41A135
E: The repository 'http://l4t-repo.nvidia.com/t234 r36.2 InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

can anyone help me to understand the procedure and resolve the issues? Thanks.

[sarodeanil35]

I have resolved the errors by copying the URL : http://l4t-repo.nvidia.com/jetson-ota-internal.key from here : http://l4t-repo.nvidia.com/

and then simply use the following command again

sudo apt-key adv --fetch-keys http://l4t-repo.nvidia.com/jetson-ota-internal.key

then

sudo apt update

does not show any errors.

but still did not understand why we had to do this.

[kesong]

@DaneLLL , Can you help to answer the question?

[DaneLLL]

Hi,
Do you flash AGX Orin developer kit through SDKManager? You should be able to execute sudo apt update without the additional steps, if the system image is installed through SDKManager.

[sarodeanil35]

Yes, I flashed the AGX Orin developer kit through SDKMangaer. Do you mean to say If flash the device through SDKManger, I do not need to follow the below steps?

step 1:
sudo apt-key adv --fetch-keys http://l4t-repo.nvidia.com/jetosn-ota-internal.key

step 2:
Add the following two lines to /etc/apt/sources.list.

 deb http://l4t-repo.nvidia.com/common r36.2 main
 deb http://l4t-repo.nvidia.com/t234 r36.2 main

Simply, do sudo apt update?

[DaneLLL]

Hi,
Yes, we expect the file is present:

/etc/apt/sources.list.d/nvidia-l4t-apt-source.list

And you can run sudo apt update directly.

[sarodeanil35]

The file

/etc/apt/sources.list.d/nvidia-l4t-apt-source.list

do exist but it has this

# SPDX-FileCopyrightText: Copyright (c) 2019-2021 NVIDIA CORPORATION & 
AFFILIATES. All rights reserved.
# SPDX-License-Identifier: LicenseRef-NvidiaProprietary
#
# NVIDIA CORPORATION, its affiliates and licensors retain all intellectual
# property and proprietary rights in and to this material, related
# documentation and any modifications thereto. Any use, reproduction,
# disclosure or distribution of this material and related documentation
# without an express license agreement from NVIDIA CORPORATION or
# its affiliates is strictly prohibited.

deb https://repo.download.nvidia.com/jetson/common r36.2 main
deb https://repo.download.nvidia.com/jetson/t234 r36.2 main

but the following lines are missing in the file

deb http://l4t-repo.nvidia.com/common r36.2 main
deb http://l4t-repo.nvidia.com/t234 r36.2 main

?

[DaneLLL]

Hi,
Please share where you see http://l4t-repo.nvidia.com. The correct website should be https://repo.download.nvidia.com. Would like to know where you see the link.

[sarodeanil35]

@DaneLLL Thanks for your patience. I think so you got confused. In my last reply, I said the file /etc/apt/sources.list.d/nvidia-l4t-apt-source.list exists and the following lines also exist

deb https://repo.download.nvidia.com/jetson/common r36.2 main
deb https://repo.download.nvidia.com/jetson/t234 r36.2 main

but as per the video(refer to my first thread ), do I need to add the following lines?

deb http://l4t-repo.nvidia.com/common r36.2 main
deb http://l4t-repo.nvidia.com/t234 r36.2 main

[kesong]

I only see this snapshot in the video. Where you see the link: http://l4t-repo.nvidia.com?

[sarodeanil35]

@kesong, I think so they removed that part from the video. I am pretty sure those steps were there. Anyways Thanks for your response.