When I run apt update I get this message
Err:1 http://cuda-internal.nvidia.com/release-candidates/kitpicks/cuda-r10-2-tegra/10.2.460/006/repos/ubuntu1804/arm64 InRelease
Could not resolve ‘cuda-internal.nvidia.com’
hi jcwscience:
do you set --net=host when run docker? can you run apt update correctly in host?
I am using net host. However I’m running an experimental arch linux build. I was hoping I could use the container to run cuda programs without using the nvidia runtime
There are several threads on this forum with the same error. In every case, nvidia support could not reproduce the error. Could it be that the cuda debian repo configured in the official L4T containers is only accessible from nvidia’s internal corporate network? When I do a manual DNS lookup on my computer (no container), I cannot resolve the hostname of the repo. I suppose this looks different for anyone who’s an nvidia employee on their work computer that uses some internal DNS server? @Jeffli
$ dig cuda-internal.nvidia.com
; <<>> DiG 9.11.3-1ubuntu1.17-Ubuntu <<>> cuda-internal.nvidia.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44989
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;cuda-internal.nvidia.com. IN A
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Jul 21 18:59:44 CEST 2022
;; MSG SIZE rcvd: 53
Hi, ahjg
This topic is not updated for some time.
Do you still meet the same error?
If yes, would you mind filing a new topic for your issue?
Thanks.
@AastaLLL
I realize this is probably an automated message that you post to stale treads, but could you confirm whether the domain cuda-internal.nvidia.com resolves for nvidia employees? I believe referencing this domain in the official containers is a bug, and only people outside the nvidia corporate network are affected by it.
Hi,
We don’t meet any error when running apt update inside the container.
Thanks.
1 Like
Thank you for trying this out! So, referencing this repo in a container intended for use outside nvidia should be considered a bug, right?
Hi,
Do you meet this issue in our recent container?
If yes, could you share which container can reproduce the problem so we can check it further?
We have tested some latest containers, for example, l4t-base:r34.1.
It uses the https://repo.download.nvidia.com/ rather than an internal link.
root@ubuntu:/# apt-get install cuda
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
...
0 upgraded, 84 newly installed, 0 to remove and 93 not upgraded.
Need to get 1459 MB of archives.
After this operation, 4218 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 https://repo.download.nvidia.com/jetson/common r34.1/main arm64 cuda-toolkit-config-common all 11.4.167-1 [16.3 kB]
Get:2 https://repo.download.nvidia.com/jetson/common r34.1/main arm64 cuda-toolkit-11-config-common all 11.4.167-1 [16.4 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 xz-utils arm64 5.2.4-1ubuntu1.1 [81.4 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 binutils-common arm64 2.34-6ubuntu1.3 [207 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 libbinutils arm64 2.34-6ubuntu1.3 [475 kB]
Get:6 https://repo.download.nvidia.com/jetson/common r34.1/main arm64 cuda-toolkit-11-4-config-common all 11.4.167-1 [16.3 kB]
Get:7 https://repo.download.nvidia.com/jetson/common r34.1/main arm64 cuda-cudart-11-4 arm64 11.4.167-1 [155 kB]
...
Thanks.
Hi, I initially encountered the issue in nvcr.io/nvidia/l4t-cuda:11.4.14-runtime. It does not seem to be present in the l4t-base containers. I have not tested any others.
I find the info page somewhat confusing, it says on the left that this container was modified on August 11, 2022, but the most recent tag is from April.
Hi,
Thanks a lot for the information.
We give the l4t-cuda:11.4.14-runtime a try and do find some internal links.
root@ubuntu:/# apt update
Get:1 https://repo.download.nvidia.com/jetson/common r34.1 InRelease [2519 B]
Ign:2 http://cuda-internal.nvidia.com/release-candidates/kitpicks/cuda-r11-4-tegra/11.4.14/009/repos/ubuntu2004/arm64 InRelease
Get:3 http://cuda-internal.nvidia.com/release-candidates/kitpicks/cuda-r11-4-tegra/11.4.14/009/repos/ubuntu2004/arm64 Release [564 B]
Get:4 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB]
Get:5 http://cuda-internal.nvidia.com/release-candidates/kitpicks/cuda-r11-4-tegra/11.4.14/009/repos/ubuntu2004/arm64 Release.gpg [836 B]
Get:6 http://cuda-internal.nvidia.com/release-candidates/kitpicks/cuda-r11-4-tegra/11.4.14/009/repos/ubuntu2004/arm64 Packages [12.3 kB]
...
We are double-checking this issue with our internal team.
Will share more information with you later.
Thanks.
1 Like
@AastaLLL : Facing the same issue with tensorrt container : 8.2.1
root@core-io:/data/home/spot/Desktop# docker run -it --network host nvcr.io/nvidia/l4t-tensorrt:r8.2.1-runtime bash
root@core-io:/# apt-get update
Err:1 http://cuda-internal.nvidia.com/release-candidates/kitpicks/tensorrt-rel-8-2-tegra/8.2.1/001/repos/l4t/arm64 InRelease
Could not resolve 'cuda-internal.nvidia.com'
Get:2 http://ports.ubuntu.com/ubuntu-ports bionic InRelease [242 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease [74.6 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease [88.7 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports bionic/universe arm64 Packages [11.0 MB]
Get:7 http://ports.ubuntu.com/ubuntu-ports bionic/multiverse arm64 Packages [153 kB]
Get:8 http://ports.ubuntu.com/ubuntu-ports bionic/restricted arm64 Packages [572 B]
Get:9 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages [1285 kB]
Get:10 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe arm64 Packages [2064 kB]
Get:11 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse arm64 Packages [5351 B]
Get:12 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages [2018 kB]
Get:13 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted arm64 Packages [5451 B]
Get:14 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe arm64 Packages [12.5 kB]
Get:15 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main arm64 Packages [12.2 kB]
Get:16 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse arm64 Packages [2761 B]
Get:17 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe arm64 Packages [1367 kB]
Get:18 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted arm64 Packages [4778 B]
Get:19 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages [1639 kB]
Fetched 20.1 MB in 24s (836 kB/s)
Reading package lists... Done
W: Failed to fetch http://cuda-internal.nvidia.com/release-candidates/kitpicks/tensorrt-rel-8-2-tegra/8.2.1/001/repos/l4t/arm64/InRelease Could not resolve 'cuda-internal.nvidia.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
I was facing the same issue, So i removed that repo’s from the source list by rm /etc/apt/source.list.d/<FILE NAME> which has this apt repo. & I added this for my TX1
echo "deb https://repo.download.nvidia.com/jetson/common r32.7 main" > /etc/apt/sources.list.d/nvidia-l4t-apt-source.list
echo "deb https://repo.download.nvidia.com/jetson/t186 r32.7 main" >> /etc/apt/sources.list.d/nvidia-l4t-apt-source.list
1 Like
I need deepstream 6.1 dockers for development, r32 seems old, i have flashed Jetpack 5.0.2 Runtime and have
in my /etc/apt/sources.list.d/nvidia-l4t-apt-source.list:
deb https://repo.download.nvidia.com/jetson/common r35.1 main
deb https://repo.download.nvidia.com/jetson/t194 r35.1 main
Can the fact that i flashed the RUNTIME version of JetPack 5.0.2 iso of Full pack cause the issue ?
(Full pack does not fit in my 16Gb jetson NX device)
I’m having the same issue as @Jcwscience. @marcel22 I have plenty of space on my Jetson and am running into the same issue.
as @gshiva5 mentioned above, you can remove the offending repo by deleting the file in /etc/apt/sources.list.d/... (and then adding the correct repo instead).
Did you remove the “cuda-internal” repos that came with the container originally? As long as they are present, apt update will fail.