Error in local apt settings

Hi All,

when using the sdkmanager to flash the Drive AGX, I get an install error for DrivePlatform Targetfs with the following message:

Error in local apt settings
SDK Manager received errors while using apt commands on your system.

Please check that the Ubuntu local apt repository is working well on your local system including dependencies of packages.

Review SDK Manager terminal for the specific error/s.

and the log NV_DRIVE_PLATFORM_RFS_TARGET_COMP.log looks like the following:

Info: [ Disk Avail:319.97 GB ]
Info: NV_DRIVE_PLATFORM_RFS_TARGET_COMP include 2 package
Info: change working directory to /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/DrivePlatform/
Info: [ Package PreInstall Started ]
Info: current working directory is /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/DrivePlatform
Info: exec_command [host]:
**********************
#!/bin/bash
set -e
if [ -d /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/DrivePlatform/ ]; then
    sudo rm -rf /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/DrivePlatform//*;
fi
**********************
Info: exec_command: /tmp/tmp_NV_DRIVE_PLATFORM_RFS_TARGET_COMP.sh
Info: [ Package PreInstall Finished Successfully ]
Info: [ Package Install Started ]
Info: DecompressInstaller starts to install package /home/srf4abt/Downloads/nvidia/sdkm_downloads/driveplatform-customtargetfs-v1.0.tar.gz
Info: finalInstallDir: /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/DrivePlatform/
Info: [ Package Install Finished Successfully ]
Info: change working directory to /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/DrivePlatform/
Info: [ Package Install Started ]
Info: current working directory is /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/DrivePlatform
Info: exec_command [host]:
**********************
#!/bin/bash
set -e
tar -zxvf /home/srf4abt/Downloads/nvidia/sdkm_downloads/driveplatform-tools-v1.0.tar.gz
cd /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/DrivePlatform//tools
sudo ./full_install_setup.sh --dualtargetfs true --symlinkoriginalpath $(dirname /home/srf4abt/Downloads/nvidia/sdkm_downloads/driveplatform-tools-v1.0.tar.gz) --driveplatformpath /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/DrivePlatform --targetfsdir /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-linux/ --printtime --nologcolors --pdkinstaller /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/pdkinstaller /home/srf4abt/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/TargetDebs
**********************
Info: exec_command: /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
e[92mINFO:e[0m Checking for prerequisites
/usr/bin/docker
e[92mINFO:e[0m Docker 19.03.1 is not installed but forceinstall was selected
e[92mINFO:e[0m 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: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]
Ign:7 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch InRelease
Hit:8 http://ubuntu-mirror.de.bosch.com/ubuntu bionic InRelease
Hit:9 http://ubuntu-mirror.de.bosch.com/ubuntu bionic-updates InRelease
Ign:10 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch-cert InRelease
Get:11 http://ubuntu-mirror.de.bosch.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:12 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch Release
Hit:13 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch-cert Release
Hit:14 http://ubuntu-mirror.de.bosch.com/multiverse bionic InRelease
Hit:16 http://ubuntu-mirror.de.bosch.com/partner bionic InRelease
Hit:17 http://ubuntu-mirror.de.bosch.com/ansible bionic InRelease
Hit:18 https://download.docker.com/linux/ubuntu bionic InRelease
Fetched 88.7 kB in 1s (65.1 kB/s)
Reading package lists...
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
Warning: apt-key output should not be parsed (stdout is not a terminal)
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
OK
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
Warning: apt-key output should not be parsed (stdout is not a terminal)
N: Ignoring file '50unattended-upgrades.ucftmp' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
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]
Ign:7 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch InRelease
Hit:8 http://ubuntu-mirror.de.bosch.com/ubuntu bionic InRelease
Hit:9 http://ubuntu-mirror.de.bosch.com/ubuntu bionic-updates InRelease
Ign:10 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch-cert InRelease
Get:11 http://ubuntu-mirror.de.bosch.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:12 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch Release
Hit:14 http://ubuntu-mirror.de.bosch.com/multiverse bionic InRelease
Hit:15 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch-cert Release
Hit:16 http://ubuntu-mirror.de.bosch.com/partner bionic InRelease
Hit:17 http://ubuntu-mirror.de.bosch.com/ansible bionic InRelease
Hit:19 https://download.docker.com/linux/ubuntu bionic InRelease
Fetched 88.7 kB in 1s (61.7 kB/s)
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 http://ubuntu-mirror.de.bosch.com/ubuntu bionic InRelease
Ign:8 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch InRelease
Hit:9 http://ubuntu-mirror.de.bosch.com/ubuntu bionic-updates InRelease
Get:10 http://ubuntu-mirror.de.bosch.com/ubuntu bionic-security InRelease [88.7 kB]
Ign:11 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch-cert InRelease
Hit:12 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch Release
Hit:13 http://ubuntu-mirror.de.bosch.com/multiverse bionic InRelease
Hit:15 http://fe0osd01.de.bosch.com/ubuntu bionic-bosch-cert Release
Hit:16 http://ubuntu-mirror.de.bosch.com/partner bionic InRelease
Hit:17 http://ubuntu-mirror.de.bosch.com/ansible bionic InRelease
Hit:18 https://download.docker.com/linux/ubuntu bionic InRelease
Fetched 88.7 kB in 1s (61.1 kB/s)
Reading package lists...
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

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:
https://docs.docker.com/get-started/

Package: qemu-user-static
Status: install ok installed
Priority: optional
Section: otherosfs
Installed-Size: 98806
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: amd64
Multi-Arch: foreign
Source: qemu
Version: 1:2.11+dfsg-1ubuntu7.23
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.3.0-6ubuntu1~18.04.1), glib2.0 (= 2.56.4-0ubuntu0.18.04.4), glibc (= 2.27-3ubuntu1.1), zlib (= 1:1.2.11.dfsg-0ubuntu2)
Homepage: http://www.qemu.org/
Original-Maintainer: Debian QEMU Team <pkg-qemu-devel@lists.alioth.debian.org>
e[92mINFO:e[0m 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.com>
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 (陳昌倬) <czchen@debian.org>
Homepage: https://github.com/stedolan/jq
e[92mINFO:e[0m jq is installed
Time to run prerequisite script: 0 minutes and 13 seconds
INFO: Starting installation step for avrfs
INFO: Installing all of the components
e[92mINFO:e[0m Building docker image.
tar: ./full_install.log: file changed as we read it
Sending build context to Docker daemon   54.9kB


Step 1/4 : FROM ubuntu:18.04
---> 72300a873c2c
Step 2/4 : ENV DEBIAN_FRONTEND=noninteractive
---> Using cache
---> d47a00c097a3
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 44ace4be5633
Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Could not resolve 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Could not resolve 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Could not resolve 'archive.ubuntu.com'
Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Could not resolve 'archive.ubuntu.com'
Reading package lists...
e[91mW: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease  Could not resolve 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease  Could not resolve 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease  Could not resolve 'archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease  Could not resolve 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
e[0mReading 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[91mEe[0me[91m: Package 'apt-utils' has no installation candidate
e[0mThe 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
e[91mERROR:e[0m 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 14 seconds
Info: [ Package Install Finished with Error ]
Info: [ 460.00 KB used. Disk Avail: 319.96 GB ]
Info: [ NV_DRIVE_PLATFORM_RFS_TARGET_COMP Install took 18s ]
Error: Run commands failed at step Install: command /tmp/tmp_NV_DRIVE_PLATFORM_RFS_TARGET_COMP.sh finished with error

Any help on how to resolve this issue is greatly appreciated!

I have same error today

Dear fixed-term.friedemann.sche,
Do you have DRIVE SW 9.0 on your target before? If not please upgrade to DRIVE SW 9.0 and then DRIVE SW 10.0. If you are moving from DRIVE SW 9.0 to DRIVE SW 10.0, could you please attach sdkm logs here(~/.nvsdkm/logs and ~/.nvsdkm/sdkm.log)?

The issue was resolved by configuring the docker proxy server properly (https://docs.docker.com/network/proxy/) for the company server.