The Docker build process has failed.

[is]

Description The Docker build process has failed.

Triton Information r23.05

Are you using the Triton container or did you build it yourself? build it in docker mode.

To Reproduce

./build.py --enable-all

Expected behavior I got the error message

 > [ 6/11] RUN curl -o /tmp/cuda-keyring.deb     https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64/cuda-keyring_1.0-1_all.deb     && apt install /tmp/cuda-keyring.deb && rm /tmp/cuda-keyring.deb &&     apt-get update && apt-get install -y datacenter-gpu-manager=1:2.4.7:
#0 0.213   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
#0 0.213                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0
#0 2.361 
#0 2.361 WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
#0 2.361 
#0 2.399 Reading package lists...
#0 3.113 E: read, still have 8 to read but none left
#0 3.113 E: Internal error, could not locate member control.tar{.zst,.lz4,.gz,.xz,.bz2,.lzma,}
#0 3.114 E: Could not read meta data from /tmp/cuda-keyring.deb
#0 3.114 E: The package lists or status file could not be parsed or opened.
------

[is]

https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64/cuda-keyring_1.0-1_all.deb requires redirection, and curl is missing the -L option.

[krishung5]

Hi @is, I wasn't able to reproduce the build issue. Could you please share the command you used to run the docker container? I'm wondering if there are any HTTP settings that might be causing a difference.

[is]

Hi @krishung5 , I also found it peculiar that nobody else seems to have a similar case. I followed the instructions as in the docuemnt.

mkdir ~/work/triton
cd ~/work/triton
git clone -b r23.05 [email protected]:triton-inference-server/server.git server
cd server
./build.py --enable-all

I built it on Aliyun ECS, perhaps it is related to this.

I executed curl -o /tmp/cuda-keyring.deb https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64/cuda-keyring_1.0-1_all.deb on host system`

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* About to connect() to developer.download.nvidia.com port 443 (#0)
*   Trying 152.199.39.144...
* Connected to developer.download.nvidia.com (152.199.39.144) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0* SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
* Server certificate:
* 	subject: CN=developer.download.nvidia.com,O=Nvidia Corporation,L=Santa Clara,ST=California,C=US
* 	start date: Dec 02 00:00:00 2022 GMT
* 	expire date: Jan 02 23:59:59 2024 GMT
* 	common name: developer.download.nvidia.com
* 	issuer: CN=DigiCert TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0> GET /compute/cuda/repos/ubuntu2204/x86_64/cuda-keyring_1.0-1_all.deb HTTP/1.1
> User-Agent: curl/7.29.0
> Host: developer.download.nvidia.com
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Content-Type: application/x-deb
< Date: Tue, 13 Jun 2023 00:52:52 GMT
< Location: https://developer.download.nvidia.cn/compute/cuda/repos/ubuntu2204/x86_64/cuda-keyring_1.0-1_all.deb
< Server: ECAcc (hkc/BD96)
< x-vdms-version: 3.48
< Content-Length: 0
< 
  0     0    0     0    0     0      0      0 --:--:--  0:00:03 --:--:--     0
* Connection #0 to host developer.download.nvidia.com left intact

It is redirected to nvidia.cn site.

[Saigut]

I meet the same problem. I use wget -O to replace curl -o to solve it. Like #5364

[Saigut]

I meet the same problem. I use wget -O to replace curl -o to solve it. Like #5364

And also curl -L -o works. @krishung5 would you like to fix it?