No access to CUDA repo from CUDA L4t docker container

This ticket is a near duplicate of this ticket.

I can do whatever I want if I use a regular ubuntu:latest container as the base container. If I want to use cuda, however, I get errors. This is the start of my docker container.

SHELL ["/bin/bash", "-c"]

I get the following error (I am running on a Jetson Orin):

W: Failed to fetch  Could not resolve ''

I am not modifying the original container - I am simply adding files to the new container in the user directories.
Here is the full error of the start of the image build process:

docker build dockerfile/ --tag cuda_ros
Sending build context to Docker daemon  7.168kB
Step 1/22 : FROM
 ---> ac921ae1d2ac
Step 2/22 : SHELL ["/bin/bash", "-c"]
 ---> Running in 5b1eabcd4f67
Removing intermediate container 5b1eabcd4f67
 ---> 3ecd75e20bfd
Step 3/22 : RUN DEBIAN_FRONTEND=noninteractive apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -qq --yes --no-install-recommends     apt-file     apt-utils     apt-transport-https
 ---> Running in 0fd5ff381a02
Err:1  InRelease
  Could not resolve ''
Get:2 bionic InRelease [242 kB]
Get:3 bionic-updates InRelease [88.7 kB]
Get:4 bionic-backports InRelease [83.3 kB]
Get:5 bionic-security InRelease [88.7 kB]
Get:6 bionic/multiverse arm64 Packages [153 kB]
Get:7 bionic/restricted arm64 Packages [572 B]
Get:8 bionic/main arm64 Packages [1285 kB]
Get:9 bionic/universe arm64 Packages [11.0 MB]
Get:10 bionic-updates/restricted arm64 Packages [5682 B]
Get:11 bionic-updates/main arm64 Packages [2093 kB]
Get:12 bionic-updates/universe arm64 Packages [2083 kB]
Get:13 bionic-updates/multiverse arm64 Packages [5351 B]
Get:14 bionic-backports/universe arm64 Packages [20.1 kB]
Get:15 bionic-backports/main arm64 Packages [64.0 kB]
Get:16 bionic-security/universe arm64 Packages [1385 kB]
Get:17 bionic-security/restricted arm64 Packages [5008 B]
Get:18 bionic-security/multiverse arm64 Packages [2761 B]
Get:19 bionic-security/main arm64 Packages [1713 kB]
Fetched 20.3 MB in 7s (3031 kB/s)
Reading package lists...
W: Failed to fetch  Could not resolve ''
W: Some index files failed to download. They have been ignored, or old ones used instead.

Is any more information required?

Hi @robotsgotmeso, can you disable that apt server by running this command in the container:

mv /etc/apt/sources.list.d/cuda.list /etc/apt/sources.list.d/cuda.disabled

After that, I’m able to run apt-get update in the container.


That appears to have gotten rid of the error messages. Is there a more long-term solution to this problem? Doesn’t this change simply lock the cuda software version from any future updates? I can see how that would be considered a good thing. Are there any other implications for this change?


That reference to that internal apt server will be removed from future versions of the container so that apt-get update works. It was used for us to build the container and not for upgrades to JetPack (for that, you could add the JetPack apt servers like l4t-jetpack container has).

That makes sense - only engineers inside the internal NVidia network would gain access to those apt servers. Thanks for the help!

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