Error installing SDK Manager and maybe apt error when create os image for Drive Platform Targetfs

Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”):
Software Version
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
[√] NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
[√] Linux
QNX
other

Hardware Platform
[√] NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
[√] 1.6.0.8170
1.5.1.7815
1.5.0.7774
other

Host Machine Version
[√] native Ubuntu 18.04
other


This the problem i met ,and i have checked the ‘apt-get’ ,Nothing unusual about it. I found out from other posts that maybe it’s a proxy setting issue, but I don’t know how to set?

Hi @fixed-term.zheng.xu,

Please provide the installation logs for our analysis. Thanks.

xhz9szh@SGHZ001013054:/tmp$ sudo /bin/bash -c /tmp/tmp_NV_DRIVE_PLATFORM_RFS_TARGET_COMP.sh
tools/
tools/prerequisite_check.sh
tools/full_install_setup.sh
tools/targetfstool_base.py
tools/Dockerfile
tools/version.py
tools/nvsciipc.cfg
tools/README.md
tools/targetfstool.py
tools/consts.py
tools/buildtracker.py
tools/docker_run_targetfstool.sh
tools/nv-run-once-install-hyperion
tools/bug_report
tools/targetfstool_drivesw_setup.py
tools/nv-run-once-add-user
tools/utilities.py
tools/.dockerignore
tools/targetfstool_avrfs_setup.py
tools/otapkg.sh
tools/common.py
tools/update_flash_config.sh
tools/x86/
tools/x86/pycache/
tools/x86/pycache/pdktool_stage_main_x86.cpython-36.pyc
tools/x86/pycache/pdktool_5_1_6_x_x86.cpython-36.pyc
tools/x86/pycache/pdktool_5_1_3_x_x86.cpython-36.pyc
tools/x86/pycache/pdktool_5_1_0_x_x86.cpython-36.pyc
tools/x86/pycache/pdktool_x86.cpython-36.pyc
tools/internal/
tools/internal/pycache/
tools/internal/pycache/pdktool_5_1_6_x_internal.cpython-36.pyc
tools/internal/pycache/pdktool_stage_main_internal.cpython-36.pyc
tools/internal/pycache/pdktool_5_1_9_x_internal.cpython-36.pyc
tools/internal/pycache/pdktool_5_1_6_1_internal.cpython-36.pyc
tools/internal/pycache/pdktool_5_1_12_x_internal.cpython-36.pyc
tools/linux/
tools/linux/targetfstool_5_1_6_x_avrfs.py
tools/linux/targetfstool_5_1_6_x_drivesw_internal.py
tools/linux/nv_ssh_rekey_run_once.sh
tools/linux/nv_ssh_rekey_run_once.service
tools/linux/nv-bom-read.sh
tools/linux/targetfstool_5_1_6_x_drivesw.py
tools/linux/misc/
tools/linux/misc/rsyslog
tools/linux/nv-bom-enter.sh
tools/linux/targetfstool_5_1_6_x_avrfs_internal.py
tools/linux/targetfstool_linux.py
tools/flash_config.json
tools/nv-mount-persfs.sh
tools/chil_setup.py
tools/nv-nameserver.sh
tools/nv-run-once-install-dpx
tools/driveav/
tools/driveav/pycache/
tools/driveav/pycache/driveav_setup.cpython-36.pyc
INFO: Skipping step 1 - building the DriveOS
INFO: Starting component install step
INFO: Running prerequisite script
INFO: Checking for prerequisites
/usr/bin/docker
INFO: Docker 19.03.1 is not installed but forceinstall was selected
INFO: Installing docker
Get:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
Ign:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
Get:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
Ign:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
Get:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
Ign:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
Hit:7 htp://mirror-osd.apac.bosch.com/ubuntu bionic InRelease
Hit:8 -security InRelease
Hit:10 -updates InRelease
Ign:11 InRelease
Hit:12 InRelease
Hit:14 h InRelease
Hit:15 bionic InRelease
Hit:16 bionic InRelease
Hit:17 bionic InRelease
Hit:19 stable InRelease
Hit:20 Release
Reading package lists…
Reading package lists…
Building dependency tree…
Reading state information…
ca-certificates is already the newest version (20210119~18.04.1).
curl is already the newest version (7.58.0-2ubuntu3.14).
software-properties-common is already the newest version (0.96.24.32.14).
apt-transport-https is already the newest version (1.6.14).
gnupg-agent is already the newest version (2.2.4-1ubuntu1.4).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Warning: apt-key output should not be parsed (stdout is not a terminal)
OK
Warning: apt-key output should not be parsed (stdout is not a terminal)
Get:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
Ign:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
Get:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
Ign:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
Get:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
Ign:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
Hit:7 htp://mirror-osd.apac.bosch.com/ubuntu bionic InRelease
Hit:9 htp://mirror-osd.apac.bosch.com/ubuntu bionic-security InRelease
Hit:10 htp://mirror-osd.apac.bosch.com/osd bionic InRelease
Hit:13 htp://mirror-osd.apac.bosch.com/partner bionic InRelease
Hit:14 htts://download.docker.com/linux/ubuntu bionic InRelease
Hit:15 htp://mirror-osd.apac.bosch.com/ansible bionic InRelease
Hit:17ttp://mirror-osd.apac.bosch.com/openconnect bionic InRelease
Hit:18 hp://mirror-osd.apac.bosch.com/cepces bionic InRelease
Hit:19 h://mirror-osd.apac.bosch.com/ms-teams stable InRelease
Hit:20 ://mirror-osd.apac.bosch.com/osd bionic Release
Reading package lists…
Get:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
Ign:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
Get:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
Ign:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
Get:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
Ign:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
Hit:7 ttp://mirror-osd.apac.bosch.com/ubuntu bionic InRelease
Hit:9 htp://mirror-osd.apac.bosch.com/ubuntu bionic-security InRelease
Hit:10 htp://mirror-osd.apac.bosch.com/ubuntu bionic-updates InRelease
Ign:11 ttp://mirror-osd.apac.bosch.com/osd bionic InRelease
Hit:13 htp://mirror-osd.apac.bosch.com/partner bionic InRelease
Hit:14 htp://mirror-osd.apac.bosch.com/ansible bionic InRelease
Hit:16 htp://mirror-osd.apac.bosch.com/openconnect bionic InRelease
Hit:17 htps://download.docker.com/linux/ubuntu bionic InRelease
Hit:18 htp://mirror-osd.apac.bosch.com/cepces bionic InRelease
Hit:19 htp://mirror-osd.apac.bosch.com/ms-teams stable InRelease
Hit:20 htp://mirror-osd.apac.bosch.com/osd bionic Release
Reading package lists…
Reading package lists…
Building dependency tree…
Reading state information…
containerd.io is already the newest version (1.4.9-1).
docker-ce-cli is already the newest version (5:19.03.15~3-0~ubuntu-bionic).
docker-ce is already the newest version (5:19.03.15~3-0~ubuntu-bionic).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:

  1. The Docker client contacted the Docker daemon.
  2. The Docker daemon pulled the “hello-world” image from the Docker Hub.
    (amd64)
  3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
  4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/

For more examples and ideas, visit:
htps://docs.docker.com/get-started/

Package: qemu-user-static
Status: install ok installed
Priority: optional
Section: otherosfs
Installed-Size: 98830
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.>
Architecture: amd64
Multi-Arch: foreign
Source: qemu
Version: 1:2.11+dfsg-1ubuntu7.37
Provides: qemu-user-binfmt
Recommends: binfmt-support
Suggests: sudo
Conflicts: qemu-user-binfmt
Description: QEMU user mode emulation binaries (static version)
QEMU is a fast processor emulator: currently the package supports
ARM, CRIS, i386, M68k (ColdFire), MicroBlaze, MIPS, PowerPC, SH4,
SPARC and x86-64 emulation. By using dynamic translation it achieves
reasonable speed while being easy to port on new host CPUs.
.
This package provides the user mode emulation binaries, built
statically. In this mode QEMU can launch Linux processes compiled for
one CPU on another CPU.
.
If binfmt-support package is installed, qemu-user-static package will
register binary formats which the provided emulators can handle, so
that it will be possible to run foreign binaries directly.
Built-Using: gcc-8 (= 8.4.0-1ubuntu1~18.04), glib2.0 (= 2.56.4-0ubuntu0.18.04.8), glibc (= 2.27-3ubuntu1.2), zlib (= 1:1.2.11.dfsg-0ubuntu2)
Homepage: htp://www.qemu.org/
Original-Maintainer: Debian QEMU Team pkg-qemu-devel@lists.alioth.debian.org
INFO: qemu-user-static is installed
Package: jq
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 88
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.>
Architecture: amd64
Multi-Arch: foreign
Version: 1.5+dfsg-2
Depends: libjq1 (= 1.5+dfsg-2), libc6 (>= 2.4)
Description: lightweight and flexible command-line JSON processor
jq is like sed for JSON data – you can use it to slice
and filter and map and transform structured data with
the same ease that sed, awk, grep and friends let you
play with text.
.
It is written in portable C, and it has minimal runtime
dependencies.
.
jq can mangle the data format that you have into the
one that you want with very little effort, and the
program to do so is often shorter and simpler than
you’d expect.
Original-Maintainer: ChangZhuo Chen (陳昌倬)
Homepage: htps://github.com/stedolan/jq
INFO: jq is installed
Time to run prerequisite script: 0 minutes and 19 seconds
INFO: Starting installation step for avrfs
INFO: Installing all of the components
INFO: Building docker image.
tar: ./full_install.log: file changed as we read it
Sending build context to Docker daemon 55.13kB
Step 1/4 : FROM ubuntu:18.04
—> 39a8cfeef173
Step 2/4 : ENV DEBIAN_FRONTEND=noninteractive
—> Using cache
—> ad9f96fb1d71
Step 3/4 : RUN apt-get update && apt-get install --yes apt-utils && apt-get install --yes python3 python3-dev qemu-user-static && apt-get autoremove --yes && apt-get clean
—> Running in 3c6b7bd08800
Err:1 htp://archive.ubuntu.com/ubuntu bionic InRelease
Could not resolve ‘archive.ubuntu.c’
Err:2 htp://archive.ubuntu.com/ubuntu bionic-updates InRelease
Could not resolve ‘archive.ubuntu.c’
Err:3 htp://security.ubuntu.com/ubuntu bionic-security InRelease
Could not resolve ‘security.ubuntu.c’
Err:4 htp://archive.ubuntu.com/ubuntu bionic-backports InRelease
Could not resolve ‘archive.ubuntu.c’
Reading package lists…
W: Failed to fetch htp://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Could not resolve ‘archive.ubuntu.c’
W: Failed to fetch htp://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Could not resolve ‘archive.ubuntu.c’
W: Failed to fetch htp://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Could not resolve ‘archive.ubuntu.’
W: Failed to fetch htp://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease Could not resolve ‘security.ubuntu.c’
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists…
Building dependency tree…
Reading state information…
Package apt-utils is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
apt

E: Package ‘apt-utils’ has no installation candidate
The command ‘/bin/sh -c apt-get update && apt-get install --yes apt-utils && apt-get install --yes python3 python3-dev qemu-user-static && apt-get autoremove --yes && apt-get clean’ returned a non-zero code: 100
ERROR: could not build docker image
INFO: Removing the docker image(s) that was just created
Total reclaimed space: 0B
ERROR: The docker failed to properly install the components
Time to failure: 0 minutes and 20 seconds
xhz9szh@SGHZ001013054:/tmp$

and because i am new user who can not send 3 links so i change some links (http or .com)

Untitled Document 1 (13.2 KB)
this is install log

Dear @fixed-term.zheng.xu,

I found out from other posts that maybe it’s a proxy setting issue, but I don’t know how to set?

Please see SDK Manager Settings :: NVIDIA SDK Manager Documentation for setting proxy.

Also, did you check the topic thread Error in local apt settings

1 Like

Hi,
I have solve the problem that caused by proxy setting issue though setting .config.json about docker