Installation error using SDKmanager

Hardware Platform: [DRIVE AGX Pegasus™ Developer Kit]
Software Version: [DRIVE Software 10]
Host Machine Version: [Ubuntu 18.04]
SDK Manager Version: [1.2.0.6738]

When using SDK manager to install, error occurs in the OS image create step.
How can I solve this problem and continue to the flashing step?

By the way, I have set the proxy in the SDK manager settings.

  • 17:09:53 INFO: Drive Platform Targetfs: archives/pulseaudio-module-bluetooth_1%3a11.1-1ubuntu7.2_arm64.deb
  • 17:09:53 INFO: Drive Platform Targetfs: archives/libxfixes-dev_1%3a5.0.3-1_arm64.deb
  • 17:09:53 INFO: Drive Platform Targetfs: archives/libxft2_2.3.2-1_arm64.deb
  • 17:09:53 INFO: Drive Platform Targetfs: archives/gnome-startup-applications_3.28.1-0ubuntu3_arm64.deb
  • 17:09:53 INFO: Drive Platform Targetfs: archives/kmod_24-1ubuntu3.2_arm64.deb
  • 17:09:53 INFO: Drive Platform Targetfs: archives/gnome-control-center-faces_1%3a3.28.2-0ubuntu0.18.04.4_all.deb
  • 17:09:53 INFO: Drive Platform Targetfs: archives/libgmime-3.0-0_3.2.0-1_arm64.deb
  • 17:09:53 INFO: Drive Platform Targetfs: archives/libshout3_2.4.1-2build1_arm64.deb
  • 17:09:53 INFO: Drive Platform Targetfs: archives/libcompizconfig0_1%3a0.9.13.1+18.04.20180302-0ubuntu1_arm64.deb
  • 17:09:53 INFO: Drive Platform Targetfs: archives/libinput10_1.10.4-1_arm64.deb
  • 17:09:54 INFO: Drive Platform Targetfs: archives/libfile-listing-perl_6.04-1_all.deb
  • 17:09:54 INFO: Drive Platform Targetfs: archives/packagekit_1.1.9-1ubuntu2.18.04.5_arm64.deb
  • 17:09:54 INFO: Drive Platform Targetfs: archives/libasound2-data_1.1.3-5ubuntu0.2_all.deb
  • 17:09:54 INFO: Drive Platform Targetfs: python/
  • 17:09:54 INFO: Drive Platform Targetfs: python/version_checker-0.6-py2.py3-none-any.whl
  • 17:09:54 INFO: Drive Platform Targetfs: python/prettytable-0.7.2.tar.bz2
  • 17:09:54 INFO: Drive Platform Targetfs: python/enum34-1.1.6-py2-none-any.whl
  • 17:09:54 INFO: Drive Platform Targetfs: python/setuptools-41.6.0-py2.py3-none-any.whl
  • 17:09:54 INFO: Drive Platform Targetfs: python/wheel-0.33.6-py2.py3-none-any.whl
  • 17:09:54 INFO: Drive Platform Targetfs: [ Package Install Finished Successfully ]
  • 17:09:54 INFO: Drive Platform Targetfs: change working directory to /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DriveSW_Components/DrivePlatform/
  • 17:09:54 INFO: Drive Platform Targetfs: [ Package Install Started ]
  • 17:09:54 INFO: Drive Platform Targetfs: current working directory is /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DriveSW_Components/DrivePlatform
  • 17:09:54 INFO: Drive Platform Targetfs: exec_command [host]:
  • 17:09:54 INFO: Drive Platform Targetfs: **********************
  • 17:09:54 INFO: Drive Platform Targetfs: #!/bin/bash
  • 17:09:54 INFO: Drive Platform Targetfs: set -e
  • 17:09:54 INFO: Drive Platform Targetfs: tar -zxvf /media/j0116030/Others/Nvidia/downloads/driveplatform-tools-v1.0.tar.gz
  • 17:09:54 INFO: Drive Platform Targetfs: cd /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DriveSW_Components/DrivePlatform//tools
  • 17:09:54 INFO: Drive Platform Targetfs: sudo ./full_install_setup.sh --dualtargetfs true --symlinkoriginalpath $(dirname /media/j0116030/Others/Nvidia/downloads/driveplatform-tools-v1.0.tar.gz) --driveplatformpath /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DriveSW_Components/DrivePlatform --targetfsdir /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DRIVEOS/drive-t186ref-linux/ --printtime --nologcolors --pdkinstaller /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DRIVEOS/pdkinstaller /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DriveSW_Components/TargetDebs
  • 17:09:54 INFO: Drive Platform Targetfs: **********************
  • 17:09:54 INFO: Drive Platform Targetfs: exec_command: /tmp/tmp_NV_DRIVE_PLATFORM_RFS_TARGET_COMP.sh
  • 17:09:54 INFO: Drive Platform Targetfs: tools/
  • 17:09:54 INFO: Drive Platform Targetfs: tools/prerequisite_check.sh
  • 17:09:54 INFO: Drive Platform Targetfs: tools/full_install_setup.sh
  • 17:09:54 INFO: Drive Platform Targetfs: tools/targetfstool_base.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/Dockerfile
  • 17:09:54 INFO: Drive Platform Targetfs: tools/version.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/nvsciipc.cfg
  • 17:09:54 INFO: Drive Platform Targetfs: tools/README.md
  • 17:09:54 INFO: Drive Platform Targetfs: tools/targetfstool.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/consts.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/buildtracker.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/docker_run_targetfstool.sh
  • 17:09:54 INFO: Drive Platform Targetfs: tools/nv-run-once-install-hyperion
  • 17:09:54 INFO: Drive Platform Targetfs: tools/bug_report
  • 17:09:54 INFO: Drive Platform Targetfs: tools/targetfstool_drivesw_setup.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/nv-run-once-add-user
  • 17:09:54 INFO: Drive Platform Targetfs: tools/utilities.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/.dockerignore
  • 17:09:54 INFO: Drive Platform Targetfs: tools/targetfstool_avrfs_setup.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/otapkg.sh
  • 17:09:54 INFO: Drive Platform Targetfs: tools/common.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/update_flash_config.sh
  • 17:09:54 INFO: Drive Platform Targetfs: tools/x86/
  • 17:09:54 INFO: Drive Platform Targetfs: tools/x86/pycache/
  • 17:09:54 INFO: Drive Platform Targetfs: tools/x86/pycache/pdktool_stage_main_x86.cpython-36.pyc
  • 17:09:54 INFO: Drive Platform Targetfs: tools/x86/pycache/pdktool_5_1_6_x_x86.cpython-36.pyc
  • 17:09:54 INFO: Drive Platform Targetfs: tools/x86/pycache/pdktool_5_1_3_x_x86.cpython-36.pyc
  • 17:09:54 INFO: Drive Platform Targetfs: tools/x86/pycache/pdktool_5_1_0_x_x86.cpython-36.pyc
  • 17:09:54 INFO: Drive Platform Targetfs: tools/x86/pycache/pdktool_x86.cpython-36.pyc
  • 17:09:54 INFO: Drive Platform Targetfs: tools/internal/
  • 17:09:54 INFO: Drive Platform Targetfs: tools/internal/pycache/
  • 17:09:54 INFO: Drive Platform Targetfs: tools/internal/pycache/pdktool_5_1_6_x_internal.cpython-36.pyc
  • 17:09:54 INFO: Drive Platform Targetfs: tools/internal/pycache/pdktool_stage_main_internal.cpython-36.pyc
  • 17:09:54 INFO: Drive Platform Targetfs: tools/internal/pycache/pdktool_5_1_9_x_internal.cpython-36.pyc
  • 17:09:54 INFO: Drive Platform Targetfs: tools/internal/pycache/pdktool_5_1_6_1_internal.cpython-36.pyc
  • 17:09:54 INFO: Drive Platform Targetfs: tools/internal/pycache/pdktool_5_1_12_x_internal.cpython-36.pyc
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/targetfstool_5_1_6_x_avrfs.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/targetfstool_5_1_6_x_drivesw_internal.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/nv_ssh_rekey_run_once.sh
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/nv_ssh_rekey_run_once.service
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/nv-bom-read.sh
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/targetfstool_5_1_6_x_drivesw.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/misc/
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/misc/rsyslog
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/nv-bom-enter.sh
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/targetfstool_5_1_6_x_avrfs_internal.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/linux/targetfstool_linux.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/flash_config.json
  • 17:09:54 INFO: Drive Platform Targetfs: tools/nv-mount-persfs.sh
  • 17:09:54 INFO: Drive Platform Targetfs: tools/chil_setup.py
  • 17:09:54 INFO: Drive Platform Targetfs: tools/nv-nameserver.sh
  • 17:09:54 INFO: Drive Platform Targetfs: tools/nv-run-once-install-dpx
  • 17:09:54 INFO: Drive Platform Targetfs: tools/driveav/
  • 17:09:54 INFO: Drive Platform Targetfs: tools/driveav/pycache/
  • 17:09:54 INFO: Drive Platform Targetfs: tools/driveav/pycache/driveav_setup.cpython-36.pyc
  • 17:09:54 INFO: Drive Platform Targetfs: INFO: Skipping step 1 - building the DriveOS
  • 17:09:54 INFO: Drive Platform Targetfs: INFO: Starting component install step
  • 17:09:54 INFO: Drive Platform Targetfs: INFO: Running prerequisite script
  • 17:09:54 INFO: Drive Platform Targetfs: INFO: Checking for prerequisites
  • 17:09:54 INFO: Drive Platform Targetfs: /usr/bin/docker
  • 17:09:54 INFO: Drive Platform Targetfs: INFO: Docker 19.03.1 is not installed but forceinstall was selected
  • 17:09:54 INFO: Drive Platform Targetfs: INFO: Installing docker
  • 17:09:54 INFO: Drive Platform Targetfs: Get:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Ign:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Get:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Ign:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Get:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Ign:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 17:09:54 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 17:09:54 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 17:09:54 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 17:09:54 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 17:09:54 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 17:09:54 INFO: Drive Platform Targetfs: Hit:7 http://jp.archive.ubuntu.com/ubuntu bionic InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Get:9 http://jp.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
  • 17:09:54 INFO: Drive Platform Targetfs: Hit:10 http://packages.microsoft.com/repos/vscode stable InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Get:11 http://jp.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
  • 17:09:54 INFO: Drive Platform Targetfs: Hit:12 http://dl.google.com/linux/chrome/deb stable InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Hit:14 https://nvidia.github.io/libnvidia-container/stable/ubuntu18.04/amd64 InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Hit:15 https://nvidia.github.io/nvidia-container-runtime/ubuntu18.04/amd64 InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Hit:16 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64 InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Hit:17 https://download.docker.com/linux/ubuntu bionic InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Hit:19 http://packages.ros.org/ros/ubuntu bionic InRelease
  • 17:09:54 INFO: Drive Platform Targetfs: Get:20 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
  • 17:09:55 INFO: Drive Platform Targetfs: Fetched 252 kB in 2s (108 kB/s)
  • 17:09:56 INFO: Drive Platform Targetfs: Reading package lists…
  • 17:09:57 INFO: Drive Platform Targetfs: Reading package lists…
  • 17:09:57 INFO: Drive Platform Targetfs: Building dependency tree…
  • 17:09:57 INFO: Drive Platform Targetfs: Reading state information…
  • 17:09:57 INFO: Drive Platform Targetfs: ca-certificates is already the newest version (20190110~18.04.1).
  • 17:09:57 INFO: Drive Platform Targetfs: curl is already the newest version (7.58.0-2ubuntu3.10).
  • 17:09:57 INFO: Drive Platform Targetfs: software-properties-common is already the newest version (0.96.24.32.14).
  • 17:09:57 INFO: Drive Platform Targetfs: apt-transport-https is already the newest version (1.6.12ubuntu0.1).
  • 17:09:57 INFO: Drive Platform Targetfs: gnupg-agent is already the newest version (2.2.4-1ubuntu1.3).
  • 17:09:57 INFO: Drive Platform Targetfs: 0 upgraded, 0 newly installed, 0 to remove and 315 not upgraded.
  • 17:09:57 INFO: Drive Platform Targetfs: curl: (6) Could not resolve host: download.docker.com
  • 17:09:57 INFO: Drive Platform Targetfs: Warning: apt-key output should not be parsed (stdout is not a terminal)
  • 17:09:57 INFO: Drive Platform Targetfs: gpg: no valid OpenPGP data found.
  • 17:09:57 INFO: Drive Platform Targetfs: Warning: apt-key output should not be parsed (stdout is not a terminal)
  • 17:09:58 INFO: Drive Platform Targetfs: Get:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Ign:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Get:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Ign:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Get:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Ign:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 17:09:59 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 17:09:59 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 17:09:59 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 17:09:59 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 17:09:59 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 17:09:59 INFO: Drive Platform Targetfs: Hit:7 http://dl.google.com/linux/chrome/deb stable InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Hit:8 http://jp.archive.ubuntu.com/ubuntu bionic InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Hit:10 http://packages.microsoft.com/repos/vscode stable InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Get:11 http://jp.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
  • 17:09:59 INFO: Drive Platform Targetfs: Hit:12 http://packages.ros.org/ros/ubuntu bionic InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Hit:13 https://nvidia.github.io/libnvidia-container/stable/ubuntu18.04/amd64 InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Hit:14 https://download.docker.com/linux/ubuntu bionic InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Hit:15 https://nvidia.github.io/nvidia-container-runtime/ubuntu18.04/amd64 InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Hit:16 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64 InRelease
  • 17:09:59 INFO: Drive Platform Targetfs: Get:17 http://jp.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
  • 17:09:59 INFO: Drive Platform Targetfs: Get:20 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
  • 17:10:05 INFO: Drive Platform Targetfs: Fetched 252 kB in 2s (101 kB/s)
  • 17:10:06 INFO: Drive Platform Targetfs: Reading package lists…
  • 17:10:07 INFO: Drive Platform Targetfs: Get:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Ign:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Get:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Ign:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Get:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Ign:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 17:10:07 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 17:10:07 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 17:10:07 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 17:10:07 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 17:10:07 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 17:10:07 INFO: Drive Platform Targetfs: Hit:7 http://jp.archive.ubuntu.com/ubuntu bionic InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Get:8 http://jp.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
  • 17:10:07 INFO: Drive Platform Targetfs: Hit:9 http://packages.microsoft.com/repos/vscode stable InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Hit:10 http://dl.google.com/linux/chrome/deb stable InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Get:12 http://jp.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
  • 17:10:07 INFO: Drive Platform Targetfs: Hit:13 https://download.docker.com/linux/ubuntu bionic InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Hit:14 https://nvidia.github.io/libnvidia-container/stable/ubuntu18.04/amd64 InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Hit:15 https://nvidia.github.io/nvidia-container-runtime/ubuntu18.04/amd64 InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Hit:16 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64 InRelease
  • 17:10:07 INFO: Drive Platform Targetfs: Hit:17 http://packages.ros.org/ros/ubuntu bionic InRelease
  • 17:10:08 INFO: Drive Platform Targetfs: Get:20 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
  • 17:10:09 INFO: Drive Platform Targetfs: Fetched 252 kB in 2s (108 kB/s)
  • 17:10:11 INFO: Drive Platform Targetfs: Reading package lists…
  • 17:10:11 INFO: Drive Platform Targetfs: Reading package lists…
  • 17:10:11 INFO: Drive Platform Targetfs: Building dependency tree…
  • 17:10:11 INFO: Drive Platform Targetfs: Reading state information…
  • 17:10:12 INFO: Drive Platform Targetfs: containerd.io is already the newest version (1.3.7-1).
  • 17:10:12 INFO: Drive Platform Targetfs: docker-ce-cli is already the newest version (5:19.03.13~3-0~ubuntu-bionic).
  • 17:10:12 INFO: Drive Platform Targetfs: docker-ce is already the newest version (5:19.03.13~3-0~ubuntu-bionic).
  • 17:10:12 INFO: Drive Platform Targetfs: 0 upgraded, 0 newly installed, 0 to remove and 315 not upgraded.
  • 17:10:15 INFO: Drive Platform Targetfs:
  • 17:10:15 INFO: Drive Platform Targetfs: Hello from Docker!
  • 17:10:15 INFO: Drive Platform Targetfs: This message shows that your installation appears to be working correctly.
  • 17:10:15 INFO: Drive Platform Targetfs:
  • 17:10:15 INFO: Drive Platform Targetfs: To generate this message, Docker took the following steps:
  • 17:10:15 INFO: Drive Platform Targetfs: 1. The Docker client contacted the Docker daemon.
  • 17:10:15 INFO: Drive Platform Targetfs: 2. The Docker daemon pulled the “hello-world” image from the Docker Hub.
  • 17:10:15 INFO: Drive Platform Targetfs: (amd64)
  • 17:10:15 INFO: Drive Platform Targetfs: 3. The Docker daemon created a new container from that image which runs the
  • 17:10:15 INFO: Drive Platform Targetfs: executable that produces the output you are currently reading.
  • 17:10:15 INFO: Drive Platform Targetfs: 4. The Docker daemon streamed that output to the Docker client, which sent it
  • 17:10:15 INFO: Drive Platform Targetfs: to your terminal.
  • 17:10:15 INFO: Drive Platform Targetfs:
  • 17:10:15 INFO: Drive Platform Targetfs: To try something more ambitious, you can run an Ubuntu container with:
  • 17:10:15 INFO: Drive Platform Targetfs: $ docker run -it ubuntu bash
  • 17:10:15 INFO: Drive Platform Targetfs:
  • 17:10:15 INFO: Drive Platform Targetfs: Share images, automate workflows, and more with a free Docker ID:
  • 17:10:15 INFO: Drive Platform Targetfs: https://hub.docker.com/
  • 17:10:15 INFO: Drive Platform Targetfs:
  • 17:10:15 INFO: Drive Platform Targetfs: For more examples and ideas, visit:
  • 17:10:15 INFO: Drive Platform Targetfs: https://docs.docker.com/get-started/
  • 17:10:15 INFO: Drive Platform Targetfs:
  • 17:10:16 INFO: Drive Platform Targetfs: Package: qemu-user-static
  • 17:10:16 INFO: Drive Platform Targetfs: Status: install ok installed
  • 17:10:17 INFO: Drive Platform Targetfs: Priority: optional
  • 17:10:17 INFO: Drive Platform Targetfs: Section: otherosfs
  • 17:10:17 INFO: Drive Platform Targetfs: Installed-Size: 98808
  • 17:10:17 INFO: Drive Platform Targetfs: Maintainer: Ubuntu Developers
  • 17:10:17 INFO: Drive Platform Targetfs: Architecture: amd64
  • 17:10:17 INFO: Drive Platform Targetfs: Multi-Arch: foreign
  • 17:10:17 INFO: Drive Platform Targetfs: Source: qemu
  • 17:10:17 INFO: Drive Platform Targetfs: Version: 1:2.11+dfsg-1ubuntu7.32
  • 17:10:17 INFO: Drive Platform Targetfs: Provides: qemu-user-binfmt
  • 17:10:17 INFO: Drive Platform Targetfs: Recommends: binfmt-support
  • 17:10:17 INFO: Drive Platform Targetfs: Suggests: sudo
  • 17:10:17 INFO: Drive Platform Targetfs: Conflicts: qemu-user-binfmt
  • 17:10:17 INFO: Drive Platform Targetfs: Description: QEMU user mode emulation binaries (static version)
  • 17:10:17 INFO: Drive Platform Targetfs: QEMU is a fast processor emulator: currently the package supports
  • 17:10:17 INFO: Drive Platform Targetfs: ARM, CRIS, i386, M68k (ColdFire), MicroBlaze, MIPS, PowerPC, SH4,
  • 17:10:17 INFO: Drive Platform Targetfs: SPARC and x86-64 emulation. By using dynamic translation it achieves
  • 17:10:17 INFO: Drive Platform Targetfs: reasonable speed while being easy to port on new host CPUs.
  • 17:10:17 INFO: Drive Platform Targetfs: .
  • 17:10:17 INFO: Drive Platform Targetfs: This package provides the user mode emulation binaries, built
  • 17:10:17 INFO: Drive Platform Targetfs: statically. In this mode QEMU can launch Linux processes compiled for
  • 17:10:17 INFO: Drive Platform Targetfs: one CPU on another CPU.
  • 17:10:17 INFO: Drive Platform Targetfs: .
  • 17:10:17 INFO: Drive Platform Targetfs: If binfmt-support package is installed, qemu-user-static package will
  • 17:10:17 INFO: Drive Platform Targetfs: register binary formats which the provided emulators can handle, so
  • 17:10:17 INFO: Drive Platform Targetfs: that it will be possible to run foreign binaries directly.
  • 17:10:17 INFO: Drive Platform Targetfs: Built-Using: gcc-8 (= 8.4.0-1ubuntu1~18.04), glib2.0 (= 2.56.4-0ubuntu0.18.04.6), glibc (= 2.27-3ubuntu1.2), zlib (= 1:1.2.11.dfsg-0ubuntu2)
  • 17:10:17 INFO: Drive Platform Targetfs: Homepage: http://www.qemu.org/
  • 17:10:17 INFO: Drive Platform Targetfs: Original-Maintainer: Debian QEMU Team
  • 17:10:17 INFO: Drive Platform Targetfs: INFO: qemu-user-static is installed
  • 17:10:17 INFO: Drive Platform Targetfs: Package: jq
  • 17:10:17 INFO: Drive Platform Targetfs: Status: install ok installed
  • 17:10:17 INFO: Drive Platform Targetfs: Priority: optional
  • 17:10:17 INFO: Drive Platform Targetfs: Section: utils
  • 17:10:17 INFO: Drive Platform Targetfs: Installed-Size: 88
  • 17:10:17 INFO: Drive Platform Targetfs: Maintainer: Ubuntu Developers
  • 17:10:17 INFO: Drive Platform Targetfs: Architecture: amd64
  • 17:10:17 INFO: Drive Platform Targetfs: Multi-Arch: foreign
  • 17:10:17 INFO: Drive Platform Targetfs: Version: 1.5+dfsg-2
  • 17:10:17 INFO: Drive Platform Targetfs: Depends: libjq1 (= 1.5+dfsg-2), libc6 (>= 2.4)
  • 17:10:17 INFO: Drive Platform Targetfs: Description: lightweight and flexible command-line JSON processor
  • 17:10:17 INFO: Drive Platform Targetfs: jq is like sed for JSON data – you can use it to slice
  • 17:10:17 INFO: Drive Platform Targetfs: and filter and map and transform structured data with
  • 17:10:17 INFO: Drive Platform Targetfs: the same ease that sed, awk, grep and friends let you
  • 17:10:17 INFO: Drive Platform Targetfs: play with text.
  • 17:10:17 INFO: Drive Platform Targetfs: .
  • 17:10:17 INFO: Drive Platform Targetfs: It is written in portable C, and it has minimal runtime
  • 17:10:17 INFO: Drive Platform Targetfs: dependencies.
  • 17:10:17 INFO: Drive Platform Targetfs: .
  • 17:10:17 INFO: Drive Platform Targetfs: jq can mangle the data format that you have into the
  • 17:10:17 INFO: Drive Platform Targetfs: one that you want with very little effort, and the
  • 17:10:17 INFO: Drive Platform Targetfs: program to do so is often shorter and simpler than
  • 17:10:17 INFO: Drive Platform Targetfs: you’d expect.
  • 17:10:17 INFO: Drive Platform Targetfs: Original-Maintainer: ChangZhuo Chen (陳昌倬)
  • 17:10:17 INFO: Drive Platform Targetfs: Homepage: https://github.com/stedolan/jq
  • 17:10:17 INFO: Drive Platform Targetfs: INFO: jq is installed
  • 17:10:17 INFO: Drive Platform Targetfs: Time to run prerequisite script: 0 minutes and 24 seconds
  • 17:10:17 INFO: Drive Platform Targetfs: INFO: Starting installation step for avrfs
  • 17:10:17 INFO: Drive Platform Targetfs: INFO: Installing all of the components
  • 17:10:17 INFO: Drive Platform Targetfs: INFO: Building docker image.
  • 17:10:17 INFO: Drive Platform Targetfs: Sending build context to Docker daemon 55.19kB
  • 17:10:17 INFO: Drive Platform Targetfs: Step 1/4 : FROM ubuntu:18.04
  • 17:10:17 INFO: Drive Platform Targetfs: —> 2eb2d388e1a2
  • 17:10:17 INFO: Drive Platform Targetfs: Step 2/4 : ENV DEBIAN_FRONTEND=noninteractive
  • 17:10:17 INFO: Drive Platform Targetfs: —> Using cache
  • 17:10:17 INFO: Drive Platform Targetfs: —> 43e66380aef6
  • 17:10:17 INFO: Drive Platform Targetfs: 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
  • 17:10:17 INFO: Drive Platform Targetfs: —> Running in 493cac0e76c0
  • 17:10:18 INFO: Drive Platform Targetfs: Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
  • 17:10:19 INFO: Drive Platform Targetfs: Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 17:10:19 INFO: Drive Platform Targetfs: Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
  • 17:10:19 INFO: Drive Platform Targetfs: Something wicked happened resolving ‘security.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 17:10:19 INFO: Drive Platform Targetfs: Err:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
  • 17:10:19 INFO: Drive Platform Targetfs: Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 17:10:19 INFO: Drive Platform Targetfs: Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
  • 17:10:19 INFO: Drive Platform Targetfs: Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 17:10:19 INFO: Drive Platform Targetfs: Reading package lists…
  • 17:10:19 INFO: Drive Platform Targetfs: W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 17:10:19 INFO: Drive Platform Targetfs: W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 17:10:19 INFO: Drive Platform Targetfs: W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 17:10:19 INFO: Drive Platform Targetfs: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease Something wicked happened resolving ‘security.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 17:10:19 INFO: Drive Platform Targetfs: W: Some index files failed to download. They have been ignored, or old ones used instead.
  • 17:10:19 INFO: Drive Platform Targetfs: Reading package lists…
  • 17:10:19 INFO: Drive Platform Targetfs: Building dependency tree…
  • 17:10:19 INFO: Drive Platform Targetfs: Reading state information…
  • 17:10:19 INFO: Drive Platform Targetfs: Package apt-utils is not available, but is referred to by another package.
  • 17:10:19 INFO: Drive Platform Targetfs: This may mean that the package is missing, has been obsoleted, or
  • 17:10:19 INFO: Drive Platform Targetfs: is only available from another source
  • 17:10:19 INFO: Drive Platform Targetfs: However the following packages replace it:
  • 17:10:19 INFO: Drive Platform Targetfs: apt
  • 17:10:19 INFO: Drive Platform Targetfs:
  • 17:10:19 INFO: Drive Platform Targetfs: E: Package ‘apt-utils’ has no installation candidate
  • 17:10:19 INFO: Drive Platform Targetfs: 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
  • 17:10:19 INFO: Drive Platform Targetfs: ERROR: could not build docker image
  • 17:10:19 INFO: Drive Platform Targetfs: INFO: Removing the docker image(s) that was just created
  • 17:10:19 INFO: Drive Platform Targetfs: Total reclaimed space: 0B
  • 17:10:19 INFO: Drive Platform Targetfs: ERROR: The docker failed to properly install the components
  • 17:10:19 INFO: Drive Platform Targetfs: Time to failure: 0 minutes and 27 seconds
  • 17:10:19 INFO: Drive Platform Targetfs: [ Package Install Finished with Error ]
  • 17:10:19 INFO: Drive Platform Targetfs: [ 508.00 KB used. Disk Avail: 134.07 GB ]
  • 17:10:19 INFO: Drive Platform Targetfs: [ NV_DRIVE_PLATFORM_RFS_TARGET_COMP Install took 33s ]
  • 17:10:19 INFO: Drive Platform Targetfs:
  • 17:10:20 SUMMARY: Drive Platform Targetfs: Failed to execute commands with GenericInstaller
  • 17:10:20 SUMMARY: Flash Xavier A+B in parallel: Depends on failed component
  • 17:10:20 SUMMARY: Drive Platform Targetfs Patch: Depends on failed component
  • 17:10:20 SUMMARY: Flash Xavier A+B in parallel: Depends on failed component

Hi @Liang_Qi,

from the log, it seems that the step where the os image creation is failing is inside the docker container (the os image is being created inside a docker container).

Please try and uninstall docker (so the sdk manager re-installs it and then will try to create the os image) and retry to install using sdk manager.
once the above phase finished successfully the sdk manager would be able to flash.

*Note: to uninstall docker(does not delete the docker images):

sudo apt-get purge -y docker-engine docker docker.io docker-ce docker-ce-cli
sudo apt-get autoremove -y --purge docker-engine docker docker.io docker-ce  

please let us know if this solved your problem.

Thanks for your reply, @shayNV

I uninstalled the docker by the command you mentioned, but the following error still occurred.

It seems that “archive.ubuntu.com” can not be accessed in step3 during the docker image creation.
I met similar problem in creating my own docker image, and solved this by add following command in dockerfile.

RUN sed -i.bak -e “s%http://archive.ubuntu.com/ubuntu/%http://ftp.iij.ad.jp/pub/linux/ubuntu/archive/%g” /etc/apt/sources.list

But I don’t know how to do this in the SDK manager auto-creating process.
Would you give me some advice?

  • 12:27:22 INFO: Drive Platform Targetfs: tools/targetfstool_base.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/Dockerfile
  • 12:27:22 INFO: Drive Platform Targetfs: tools/version.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/nvsciipc.cfg
  • 12:27:22 INFO: Drive Platform Targetfs: tools/README.md
  • 12:27:22 INFO: Drive Platform Targetfs: tools/targetfstool.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/consts.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/buildtracker.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/docker_run_targetfstool.sh
  • 12:27:22 INFO: Drive Platform Targetfs: tools/nv-run-once-install-hyperion
  • 12:27:22 INFO: Drive Platform Targetfs: tools/bug_report
  • 12:27:22 INFO: Drive Platform Targetfs: tools/targetfstool_drivesw_setup.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/nv-run-once-add-user
  • 12:27:22 INFO: Drive Platform Targetfs: tools/utilities.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/.dockerignore
  • 12:27:22 INFO: Drive Platform Targetfs: tools/targetfstool_avrfs_setup.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/otapkg.sh
  • 12:27:22 INFO: Drive Platform Targetfs: tools/common.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/update_flash_config.sh
  • 12:27:22 INFO: Drive Platform Targetfs: tools/x86/
  • 12:27:22 INFO: Drive Platform Targetfs: tools/x86/pycache/
  • 12:27:22 INFO: Drive Platform Targetfs: tools/x86/pycache/pdktool_stage_main_x86.cpython-36.pyc
  • 12:27:22 INFO: Drive Platform Targetfs: tools/x86/pycache/pdktool_5_1_6_x_x86.cpython-36.pyc
  • 12:27:22 INFO: Drive Platform Targetfs: tools/x86/pycache/pdktool_5_1_3_x_x86.cpython-36.pyc
  • 12:27:22 INFO: Drive Platform Targetfs: tools/x86/pycache/pdktool_5_1_0_x_x86.cpython-36.pyc
  • 12:27:22 INFO: Drive Platform Targetfs: tools/x86/pycache/pdktool_x86.cpython-36.pyc
  • 12:27:22 INFO: Drive Platform Targetfs: tools/internal/
  • 12:27:22 INFO: Drive Platform Targetfs: tools/internal/pycache/
  • 12:27:22 INFO: Drive Platform Targetfs: tools/internal/pycache/pdktool_5_1_6_x_internal.cpython-36.pyc
  • 12:27:22 INFO: Drive Platform Targetfs: tools/internal/pycache/pdktool_stage_main_internal.cpython-36.pyc
  • 12:27:22 INFO: Drive Platform Targetfs: tools/internal/pycache/pdktool_5_1_9_x_internal.cpython-36.pyc
  • 12:27:22 INFO: Drive Platform Targetfs: tools/internal/pycache/pdktool_5_1_6_1_internal.cpython-36.pyc
  • 12:27:22 INFO: Drive Platform Targetfs: tools/internal/pycache/pdktool_5_1_12_x_internal.cpython-36.pyc
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/targetfstool_5_1_6_x_avrfs.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/targetfstool_5_1_6_x_drivesw_internal.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/nv_ssh_rekey_run_once.sh
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/nv_ssh_rekey_run_once.service
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/nv-bom-read.sh
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/targetfstool_5_1_6_x_drivesw.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/misc/
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/misc/rsyslog
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/nv-bom-enter.sh
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/targetfstool_5_1_6_x_avrfs_internal.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/linux/targetfstool_linux.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/flash_config.json
  • 12:27:22 INFO: Drive Platform Targetfs: tools/nv-mount-persfs.sh
  • 12:27:22 INFO: Drive Platform Targetfs: tools/chil_setup.py
  • 12:27:22 INFO: Drive Platform Targetfs: tools/nv-nameserver.sh
  • 12:27:22 INFO: Drive Platform Targetfs: tools/nv-run-once-install-dpx
  • 12:27:22 INFO: Drive Platform Targetfs: tools/driveav/
  • 12:27:22 INFO: Drive Platform Targetfs: tools/driveav/pycache/
  • 12:27:22 INFO: Drive Platform Targetfs: tools/driveav/pycache/driveav_setup.cpython-36.pyc
  • 12:27:22 INFO: Drive Platform Targetfs: INFO: Skipping step 1 - building the DriveOS
  • 12:27:22 INFO: Drive Platform Targetfs: INFO: Starting component install step
  • 12:27:22 INFO: Drive Platform Targetfs: INFO: Running prerequisite script
  • 12:27:22 INFO: Drive Platform Targetfs: INFO: Checking for prerequisites
  • 12:27:22 INFO: Drive Platform Targetfs: INFO: Docker 19.03.1 is not installed but forceinstall was selected
  • 12:27:22 INFO: Drive Platform Targetfs: INFO: Installing docker
  • 12:27:22 INFO: Drive Platform Targetfs: Get:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Ign:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Get:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Ign:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Get:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Ign:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 12:27:22 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 12:27:22 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 12:27:22 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 12:27:22 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 12:27:22 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 12:27:22 INFO: Drive Platform Targetfs: Hit:7 http://jp.archive.ubuntu.com/ubuntu bionic InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Hit:8 http://jp.archive.ubuntu.com/ubuntu bionic-updates InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Hit:9 http://dl.google.com/linux/chrome/deb stable InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Hit:10 http://packages.microsoft.com/repos/vscode stable InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Hit:11 http://jp.archive.ubuntu.com/ubuntu bionic-backports InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Hit:13 https://nvidia.github.io/libnvidia-container/stable/ubuntu18.04/amd64 InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Hit:14 https://download.docker.com/linux/ubuntu bionic InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Hit:15 https://nvidia.github.io/nvidia-container-runtime/ubuntu18.04/amd64 InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Hit:16 http://security.ubuntu.com/ubuntu bionic-security InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Hit:17 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64 InRelease
  • 12:27:22 INFO: Drive Platform Targetfs: Hit:19 http://packages.ros.org/ros/ubuntu bionic InRelease
  • 12:27:26 INFO: Drive Platform Targetfs: Reading package lists…
  • 12:27:26 INFO: Drive Platform Targetfs: Reading package lists…
  • 12:27:26 INFO: Drive Platform Targetfs: Building dependency tree…
  • 12:27:26 INFO: Drive Platform Targetfs: Reading state information…
  • 12:27:27 INFO: Drive Platform Targetfs: ca-certificates is already the newest version (20190110~18.04.1).
  • 12:27:27 INFO: Drive Platform Targetfs: curl is already the newest version (7.58.0-2ubuntu3.10).
  • 12:27:27 INFO: Drive Platform Targetfs: software-properties-common is already the newest version (0.96.24.32.14).
  • 12:27:27 INFO: Drive Platform Targetfs: apt-transport-https is already the newest version (1.6.12ubuntu0.1).
  • 12:27:27 INFO: Drive Platform Targetfs: gnupg-agent is already the newest version (2.2.4-1ubuntu1.3).
  • 12:27:27 INFO: Drive Platform Targetfs: 0 upgraded, 0 newly installed, 0 to remove and 318 not upgraded.
  • 12:27:27 INFO: Drive Platform Targetfs: curl: (6) Could not resolve host: download.docker.com
  • 12:27:27 INFO: Drive Platform Targetfs: Warning: apt-key output should not be parsed (stdout is not a terminal)
  • 12:27:27 INFO: Drive Platform Targetfs: gpg: no valid OpenPGP data found.
  • 12:27:27 INFO: Drive Platform Targetfs: Warning: apt-key output should not be parsed (stdout is not a terminal)
  • 12:27:28 INFO: Drive Platform Targetfs: Get:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Ign:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Get:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Ign:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Get:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Ign:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 12:27:28 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 12:27:28 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 12:27:28 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 12:27:28 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 12:27:28 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 12:27:28 INFO: Drive Platform Targetfs: Hit:7 http://jp.archive.ubuntu.com/ubuntu bionic InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Hit:8 http://jp.archive.ubuntu.com/ubuntu bionic-updates InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Hit:9 http://dl.google.com/linux/chrome/deb stable InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Hit:10 http://jp.archive.ubuntu.com/ubuntu bionic-backports InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Hit:12 http://packages.microsoft.com/repos/vscode stable InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Hit:13 http://security.ubuntu.com/ubuntu bionic-security InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Hit:14 https://download.docker.com/linux/ubuntu bionic InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Hit:15 https://nvidia.github.io/libnvidia-container/stable/ubuntu18.04/amd64 InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Hit:16 https://nvidia.github.io/nvidia-container-runtime/ubuntu18.04/amd64 InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Hit:18 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64 InRelease
  • 12:27:28 INFO: Drive Platform Targetfs: Hit:19 http://packages.ros.org/ros/ubuntu bionic InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Reading package lists…
  • 12:27:36 INFO: Drive Platform Targetfs: Get:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Ign:1 file:/var/cuda-repo-10-2-local-10.2.19-430.17 InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Get:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Ign:2 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Get:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Ign:3 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 12:27:36 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 12:27:36 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 12:27:36 INFO: Drive Platform Targetfs: Get:4 file:/var/cuda-repo-10-2-local-10.2.19-430.17 Release [574 B]
  • 12:27:36 INFO: Drive Platform Targetfs: Get:5 file:/var/cuda-repo-10-2-local-10.2.19-cross-aarch64 Release [574 B]
  • 12:27:36 INFO: Drive Platform Targetfs: Get:6 file:/var/nv-tensorrt-repo-cuda10.2-trt5.1.4.2-ga-20190506 Release [574 B]
  • 12:27:36 INFO: Drive Platform Targetfs: Hit:7 http://jp.archive.ubuntu.com/ubuntu bionic InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Hit:8 http://dl.google.com/linux/chrome/deb stable InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Hit:9 http://jp.archive.ubuntu.com/ubuntu bionic-updates InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Hit:10 http://jp.archive.ubuntu.com/ubuntu bionic-backports InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Hit:11 http://packages.microsoft.com/repos/vscode stable InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Hit:13 http://security.ubuntu.com/ubuntu bionic-security InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Hit:14 https://download.docker.com/linux/ubuntu bionic InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Hit:15 https://nvidia.github.io/libnvidia-container/stable/ubuntu18.04/amd64 InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Hit:17 https://nvidia.github.io/nvidia-container-runtime/ubuntu18.04/amd64 InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Hit:18 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64 InRelease
  • 12:27:36 INFO: Drive Platform Targetfs: Hit:19 http://packages.ros.org/ros/ubuntu bionic InRelease
  • 12:27:40 INFO: Drive Platform Targetfs: Reading package lists…
  • 12:27:40 INFO: Drive Platform Targetfs: Reading package lists…
  • 12:27:40 INFO: Drive Platform Targetfs: Building dependency tree…
  • 12:27:40 INFO: Drive Platform Targetfs: Reading state information…
  • 12:27:41 INFO: Drive Platform Targetfs: containerd.io is already the newest version (1.3.7-1).
  • 12:27:41 INFO: Drive Platform Targetfs: The following additional packages will be installed:
  • 12:27:41 INFO: Drive Platform Targetfs: aufs-tools cgroupfs-mount pigz
  • 12:27:41 INFO: Drive Platform Targetfs: The following NEW packages will be installed:
  • 12:27:41 INFO: Drive Platform Targetfs: aufs-tools cgroupfs-mount docker-ce docker-ce-cli pigz
  • 12:27:41 INFO: Drive Platform Targetfs: 0 upgraded, 5 newly installed, 0 to remove and 318 not upgraded.
  • 12:27:41 INFO: Drive Platform Targetfs: Need to get 0 B/66.9 MB of archives.
  • 12:27:41 INFO: Drive Platform Targetfs: After this operation, 295 MB of additional disk space will be used.
  • 12:27:41 INFO: Drive Platform Targetfs: Selecting previously unselected package pigz.
  • 12:27:42 INFO: Drive Platform Targetfs: (Reading database … (Reading database … 5% (Reading database … 10% (Reading database … 15% (Reading database … 20% (Reading database … 25% (Reading database … 30% (Reading database … 35% (Reading database … 40% (Reading database … 45% (Reading database … 50% (Reading database … 55% (Reading database … 60% (Reading database … 65% (Reading database … 70% (Reading database … 75% (Reading database … 80% (Reading database … 85% (Reading database … 90% (Reading database … 95% (Reading database … 100% (Reading database … 354392 files and directories currently installed.)
  • 12:27:42 INFO: Drive Platform Targetfs: Preparing to unpack …/archives/pigz_2.4-1_amd64.deb …
  • 12:27:42 INFO: Drive Platform Targetfs: Unpacking pigz (2.4-1) …
  • 12:27:42 INFO: Drive Platform Targetfs: Selecting previously unselected package aufs-tools.
  • 12:27:42 INFO: Drive Platform Targetfs: Preparing to unpack …/aufs-tools_1%3a4.9+20170918-1ubuntu1_amd64.deb …
  • 12:27:42 INFO: Drive Platform Targetfs: Unpacking aufs-tools (1:4.9+20170918-1ubuntu1) …
  • 12:27:43 INFO: Drive Platform Targetfs: Selecting previously unselected package cgroupfs-mount.
  • 12:27:43 INFO: Drive Platform Targetfs: Preparing to unpack …/cgroupfs-mount_1.4_all.deb …
  • 12:27:43 INFO: Drive Platform Targetfs: Unpacking cgroupfs-mount (1.4) …
  • 12:27:43 INFO: Drive Platform Targetfs: Selecting previously unselected package docker-ce-cli.
  • 12:27:44 INFO: Drive Platform Targetfs: Preparing to unpack …/docker-ce-cli_5%3a19.03.13~3-0~ubuntu-bionic_amd64.deb …
  • 12:27:44 INFO: Drive Platform Targetfs: Unpacking docker-ce-cli (5:19.03.13~3-0~ubuntu-bionic) …
  • 12:27:48 INFO: Drive Platform Targetfs: Selecting previously unselected package docker-ce.
  • 12:27:48 INFO: Drive Platform Targetfs: Preparing to unpack …/docker-ce_5%3a19.03.13~3-0~ubuntu-bionic_amd64.deb …
  • 12:27:48 INFO: Drive Platform Targetfs: Unpacking docker-ce (5:19.03.13~3-0~ubuntu-bionic) …
  • 12:27:51 INFO: Drive Platform Targetfs: Setting up aufs-tools (1:4.9+20170918-1ubuntu1) …
  • 12:27:52 INFO: Drive Platform Targetfs: Setting up cgroupfs-mount (1.4) …
  • 12:27:52 INFO: Drive Platform Targetfs: Setting up docker-ce-cli (5:19.03.13~3-0~ubuntu-bionic) …
  • 12:27:52 INFO: Drive Platform Targetfs: Setting up pigz (2.4-1) …
  • 12:27:53 INFO: Drive Platform Targetfs: Setting up docker-ce (5:19.03.13~3-0~ubuntu-bionic) …
  • 12:27:53 INFO: Drive Platform Targetfs: Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
  • 12:27:53 INFO: Drive Platform Targetfs: Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
  • 12:27:58 INFO: Drive Platform Targetfs: Processing triggers for libc-bin (2.27-3ubuntu1.2) …
  • 12:27:59 INFO: Drive Platform Targetfs: /sbin/ldconfig.real: file /usr/local/driveworks-2.2/./targets/x86_64-Linux/lib/libnvinfer.so.5 is truncated
  • 12:27:59 INFO: Drive Platform Targetfs:
  • 12:27:59 INFO: Drive Platform Targetfs: /sbin/ldconfig.real: file /usr/local/driveworks-2.2/./targets/x86_64-Linux/lib/libnvinfer.so.5.1.4 is truncated
  • 12:27:59 INFO: Drive Platform Targetfs:
  • 12:27:59 INFO: Drive Platform Targetfs: /sbin/ldconfig.real: file /usr/local/driveworks-2.2/./targets/x86_64-Linux/lib/libnvisp_cuda.so is truncated
  • 12:27:59 INFO: Drive Platform Targetfs:
  • 12:27:59 INFO: Drive Platform Targetfs: /sbin/ldconfig.real: /usr/local/driveworks-2.2/./targets/x86_64-Linux/lib/ is not a symbolic link
  • 12:27:59 INFO: Drive Platform Targetfs:
  • 12:27:59 INFO: Drive Platform Targetfs: Processing triggers for systemd (237-3ubuntu10.41) …
  • 12:27:59 INFO: Drive Platform Targetfs: Processing triggers for man-db (2.8.3-2ubuntu0.1) …
  • 12:28:03 INFO: Drive Platform Targetfs: Processing triggers for ureadahead (0.100.0-21) …
  • 12:28:07 INFO: Drive Platform Targetfs:
  • 12:28:07 INFO: Drive Platform Targetfs: Hello from Docker!
  • 12:28:07 INFO: Drive Platform Targetfs: This message shows that your installation appears to be working correctly.
  • 12:28:07 INFO: Drive Platform Targetfs:
  • 12:28:07 INFO: Drive Platform Targetfs: To generate this message, Docker took the following steps:
  • 12:28:07 INFO: Drive Platform Targetfs: 1. The Docker client contacted the Docker daemon.
  • 12:28:07 INFO: Drive Platform Targetfs: 2. The Docker daemon pulled the “hello-world” image from the Docker Hub.
  • 12:28:07 INFO: Drive Platform Targetfs: (amd64)
  • 12:28:07 INFO: Drive Platform Targetfs: 3. The Docker daemon created a new container from that image which runs the
  • 12:28:07 INFO: Drive Platform Targetfs: executable that produces the output you are currently reading.
  • 12:28:07 INFO: Drive Platform Targetfs: 4. The Docker daemon streamed that output to the Docker client, which sent it
  • 12:28:07 INFO: Drive Platform Targetfs: to your terminal.
  • 12:28:07 INFO: Drive Platform Targetfs:
  • 12:28:07 INFO: Drive Platform Targetfs: To try something more ambitious, you can run an Ubuntu container with:
  • 12:28:07 INFO: Drive Platform Targetfs: $ docker run -it ubuntu bash
  • 12:28:07 INFO: Drive Platform Targetfs:
  • 12:28:07 INFO: Drive Platform Targetfs: Share images, automate workflows, and more with a free Docker ID:
  • 12:28:07 INFO: Drive Platform Targetfs: https://hub.docker.com/
  • 12:28:07 INFO: Drive Platform Targetfs:
  • 12:28:07 INFO: Drive Platform Targetfs: For more examples and ideas, visit:
  • 12:28:07 INFO: Drive Platform Targetfs: https://docs.docker.com/get-started/
  • 12:28:07 INFO: Drive Platform Targetfs:
  • 12:28:09 INFO: Drive Platform Targetfs: Package: qemu-user-static
  • 12:28:09 INFO: Drive Platform Targetfs: Status: install ok installed
  • 12:28:09 INFO: Drive Platform Targetfs: Priority: optional
  • 12:28:09 INFO: Drive Platform Targetfs: Section: otherosfs
  • 12:28:09 INFO: Drive Platform Targetfs: Installed-Size: 98808
  • 12:28:09 INFO: Drive Platform Targetfs: Maintainer: Ubuntu Developers
  • 12:28:09 INFO: Drive Platform Targetfs: Architecture: amd64
  • 12:28:09 INFO: Drive Platform Targetfs: Multi-Arch: foreign
  • 12:28:09 INFO: Drive Platform Targetfs: Source: qemu
  • 12:28:09 INFO: Drive Platform Targetfs: Version: 1:2.11+dfsg-1ubuntu7.32
  • 12:28:09 INFO: Drive Platform Targetfs: Provides: qemu-user-binfmt
  • 12:28:09 INFO: Drive Platform Targetfs: Recommends: binfmt-support
  • 12:28:09 INFO: Drive Platform Targetfs: Suggests: sudo
  • 12:28:09 INFO: Drive Platform Targetfs: Conflicts: qemu-user-binfmt
  • 12:28:09 INFO: Drive Platform Targetfs: Description: QEMU user mode emulation binaries (static version)
  • 12:28:09 INFO: Drive Platform Targetfs: QEMU is a fast processor emulator: currently the package supports
  • 12:28:09 INFO: Drive Platform Targetfs: ARM, CRIS, i386, M68k (ColdFire), MicroBlaze, MIPS, PowerPC, SH4,
  • 12:28:09 INFO: Drive Platform Targetfs: SPARC and x86-64 emulation. By using dynamic translation it achieves
  • 12:28:09 INFO: Drive Platform Targetfs: reasonable speed while being easy to port on new host CPUs.
  • 12:28:09 INFO: Drive Platform Targetfs: .
  • 12:28:09 INFO: Drive Platform Targetfs: This package provides the user mode emulation binaries, built
  • 12:28:09 INFO: Drive Platform Targetfs: statically. In this mode QEMU can launch Linux processes compiled for
  • 12:28:09 INFO: Drive Platform Targetfs: one CPU on another CPU.
  • 12:28:09 INFO: Drive Platform Targetfs: .
  • 12:28:09 INFO: Drive Platform Targetfs: If binfmt-support package is installed, qemu-user-static package will
  • 12:28:09 INFO: Drive Platform Targetfs: register binary formats which the provided emulators can handle, so
  • 12:28:09 INFO: Drive Platform Targetfs: that it will be possible to run foreign binaries directly.
  • 12:28:09 INFO: Drive Platform Targetfs: Built-Using: gcc-8 (= 8.4.0-1ubuntu1~18.04), glib2.0 (= 2.56.4-0ubuntu0.18.04.6), glibc (= 2.27-3ubuntu1.2), zlib (= 1:1.2.11.dfsg-0ubuntu2)
  • 12:28:09 INFO: Drive Platform Targetfs: Homepage: http://www.qemu.org/
  • 12:28:09 INFO: Drive Platform Targetfs: Original-Maintainer: Debian QEMU Team
  • 12:28:09 INFO: Drive Platform Targetfs: INFO: qemu-user-static is installed
  • 12:28:09 INFO: Drive Platform Targetfs: Package: jq
  • 12:28:09 INFO: Drive Platform Targetfs: Status: install ok installed
  • 12:28:09 INFO: Drive Platform Targetfs: Priority: optional
  • 12:28:09 INFO: Drive Platform Targetfs: Section: utils
  • 12:28:09 INFO: Drive Platform Targetfs: Installed-Size: 88
  • 12:28:09 INFO: Drive Platform Targetfs: Maintainer: Ubuntu Developers
  • 12:28:09 INFO: Drive Platform Targetfs: Architecture: amd64
  • 12:28:09 INFO: Drive Platform Targetfs: Multi-Arch: foreign
  • 12:28:09 INFO: Drive Platform Targetfs: Version: 1.5+dfsg-2
  • 12:28:09 INFO: Drive Platform Targetfs: Depends: libjq1 (= 1.5+dfsg-2), libc6 (>= 2.4)
  • 12:28:09 INFO: Drive Platform Targetfs: Description: lightweight and flexible command-line JSON processor
  • 12:28:09 INFO: Drive Platform Targetfs: jq is like sed for JSON data – you can use it to slice
  • 12:28:09 INFO: Drive Platform Targetfs: and filter and map and transform structured data with
  • 12:28:09 INFO: Drive Platform Targetfs: the same ease that sed, awk, grep and friends let you
  • 12:28:09 INFO: Drive Platform Targetfs: play with text.
  • 12:28:09 INFO: Drive Platform Targetfs: .
  • 12:28:09 INFO: Drive Platform Targetfs: It is written in portable C, and it has minimal runtime
  • 12:28:09 INFO: Drive Platform Targetfs: dependencies.
  • 12:28:09 INFO: Drive Platform Targetfs: .
  • 12:28:09 INFO: Drive Platform Targetfs: jq can mangle the data format that you have into the
  • 12:28:09 INFO: Drive Platform Targetfs: one that you want with very little effort, and the
  • 12:28:09 INFO: Drive Platform Targetfs: program to do so is often shorter and simpler than
  • 12:28:09 INFO: Drive Platform Targetfs: you’d expect.
  • 12:28:09 INFO: Drive Platform Targetfs: Original-Maintainer: ChangZhuo Chen (陳昌倬)
  • 12:28:09 INFO: Drive Platform Targetfs: Homepage: https://github.com/stedolan/jq
  • 12:28:09 INFO: Drive Platform Targetfs: INFO: jq is installed
  • 12:28:09 INFO: Drive Platform Targetfs: Time to run prerequisite script: 0 minutes and 47 seconds
  • 12:28:09 INFO: Drive Platform Targetfs: INFO: Starting installation step for avrfs
  • 12:28:09 INFO: Drive Platform Targetfs: INFO: Installing all of the components
  • 12:28:09 INFO: Drive Platform Targetfs: INFO: Building docker image.
  • 12:28:09 INFO: Drive Platform Targetfs: Sending build context to Docker daemon 55.75kB
  • 12:28:09 INFO: Drive Platform Targetfs: Step 1/4 : FROM ubuntu:18.04
  • 12:28:09 INFO: Drive Platform Targetfs: —> 2eb2d388e1a2
  • 12:28:09 INFO: Drive Platform Targetfs: Step 2/4 : ENV DEBIAN_FRONTEND=noninteractive
  • 12:28:09 INFO: Drive Platform Targetfs: —> Using cache
  • 12:28:09 INFO: Drive Platform Targetfs: —> 43e66380aef6
  • 12:28:09 INFO: Drive Platform Targetfs: 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
  • 12:28:10 INFO: Drive Platform Targetfs: —> Running in 83b2a02d478c
  • 12:28:11 INFO: Drive Platform Targetfs: Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
  • 12:28:11 INFO: Drive Platform Targetfs: Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 12:28:11 INFO: Drive Platform Targetfs: Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
  • 12:28:11 INFO: Drive Platform Targetfs: Something wicked happened resolving ‘security.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 12:28:11 INFO: Drive Platform Targetfs: Err:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
  • 12:28:11 INFO: Drive Platform Targetfs: Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 12:28:11 INFO: Drive Platform Targetfs: Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
  • 12:28:11 INFO: Drive Platform Targetfs: Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 12:28:11 INFO: Drive Platform Targetfs: Reading package lists…
  • 12:28:11 INFO: Drive Platform Targetfs: W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 12:28:11 INFO: Drive Platform Targetfs: W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 12:28:11 INFO: Drive Platform Targetfs: W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Something wicked happened resolving ‘archive.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 12:28:11 INFO: Drive Platform Targetfs: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease Something wicked happened resolving ‘security.ubuntu.com:80’ (-5 - No address associated with hostname)
  • 12:28:11 INFO: Drive Platform Targetfs: W: Some index files failed to download. They have been ignored, or old ones used instead.
  • 12:28:11 INFO: Drive Platform Targetfs: Reading package lists…
  • 12:28:11 INFO: Drive Platform Targetfs: Building dependency tree…
  • 12:28:11 INFO: Drive Platform Targetfs: Reading state information…
  • 12:28:11 INFO: Drive Platform Targetfs: Package apt-utils is not available, but is referred to by another package.
  • 12:28:11 INFO: Drive Platform Targetfs: This may mean that the package is missing, has been obsoleted, or
  • 12:28:11 INFO: Drive Platform Targetfs: is only available from another source
  • 12:28:11 INFO: Drive Platform Targetfs: However the following packages replace it:
  • 12:28:11 INFO: Drive Platform Targetfs: apt
  • 12:28:11 INFO: Drive Platform Targetfs:
  • 12:28:11 INFO: Drive Platform Targetfs: E: Package ‘apt-utils’ has no installation candidate
  • 12:28:12 INFO: Drive Platform Targetfs: 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
  • 12:28:12 INFO: Drive Platform Targetfs: ERROR: could not build docker image
  • 12:28:12 INFO: Drive Platform Targetfs: INFO: Removing the docker image(s) that was just created
  • 12:28:12 INFO: Drive Platform Targetfs: Total reclaimed space: 0B
  • 12:28:12 INFO: Drive Platform Targetfs: ERROR: The docker failed to properly install the components
  • 12:28:12 INFO: Drive Platform Targetfs: Time to failure: 0 minutes and 50 seconds
  • 12:28:12 INFO: Drive Platform Targetfs: [ Package Install Finished with Error ]
  • 12:28:12 INFO: Drive Platform Targetfs: [ 282.40 MB used. Disk Avail: 134.05 GB ]
  • 12:28:12 INFO: Drive Platform Targetfs: [ NV_DRIVE_PLATFORM_RFS_TARGET_COMP Install took 52s ]
  • 12:28:12 INFO: Drive Platform Targetfs:
  • 12:28:12 SUMMARY: Drive Platform Targetfs: Failed to execute commands with GenericInstaller
  • 12:28:12 SUMMARY: Flash Xavier A+B in parallel: Depends on failed component
  • 12:28:12 SUMMARY: Drive Platform Targetfs Patch: Depends on failed component
  • 12:28:12 SUMMARY: Flash Xavier A+B in parallel: Depends on failed component

Hi @Liang_Qi,

I see the same error occurs.

It seems the problem is that the docker is not able to access the external internet.

please make sure you are connected to the internet when you run the installation and there is no firewall that is bloacking docker from accessing the internet. and update if it is solved

Hi @shayNV
It seems that the proxy setting is not copied to docker.
I finally solve this problem by replace the dockerfile by a copy with proxy setting added.
I can continue now but another error occurred during the flashing process.

It seems [Component PreInstall] has some error, but I don’t know what exactly it is and how to fix it.

  • 11:56:57 INFO: null
  • 11:57:02 SUMMARY: CUDA on Host: Install completed successfully.
  • 11:57:02 SUMMARY: CUDA Cross Compile for Linux: Install completed successfully.
  • 11:57:02 SUMMARY: cuDNN Cross Compile for Linux: Install completed successfully.
  • 11:57:02 SUMMARY: TensorRT (with cuDNN 7.5) x86: Install completed successfully.
  • 11:57:02 SUMMARY: TensorRT Cross Compile for Linux: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE AV on Host: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE AV Cross Compile for Linux: Install completed successfully.
  • 11:57:02 SUMMARY: DriveWorks Documentation: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE AV App Documentation: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE AR SDK: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE AR Cross Compile for Linux: Install completed successfully.
  • 11:57:02 SUMMARY: NVIDIA Nsight Graphics: Install completed successfully.
  • 11:57:02 SUMMARY: NVIDIA Nsight Systems: Install completed successfully.
  • 11:57:02 SUMMARY: GNU Toolchains: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE Foundation Packages: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE Foundation OSS Packages: Install completed successfully.
  • 11:57:02 SUMMARY: P3479 specific package: Install completed successfully.
  • 11:57:02 SUMMARY: E3550 specific package: Install completed successfully.
  • 11:57:02 SUMMARY: Flash Tools: Install completed successfully.
  • 11:57:02 SUMMARY: OSS and NV packages: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE AGX Packages: Install completed successfully.
  • 11:57:02 SUMMARY: Aurix Updater: Install completed successfully.
  • 11:57:02 SUMMARY: DDS Framework: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE Linux Release Notes: Install completed successfully.
  • 11:57:02 SUMMARY: CUDA on Target: Install completed successfully.
  • 11:57:02 SUMMARY: TensorRT (with cuDNN 7.5) on Target: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE AV on Target: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE IX SDK: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE AR on Target: Install completed successfully.
  • 11:57:02 SUMMARY: DRIVE UX on Target: Install completed successfully.
  • 11:57:02 SUMMARY: Drive Platform Targetfs: Install completed successfully.
  • 11:57:02 SUMMARY: Drive Platform Targetfs Patch: Install completed successfully.
  • 11:57:02 SUMMARY: HYPERION-7.1: Install completed successfully.
  • 11:57:02 SUMMARY: Service Framework: Install completed successfully.
  • 11:57:02 SUMMARY: Drive OTA: Install completed successfully.
  • 11:57:19 DEBUG: Flash Xavier A+B in parallel: using adapter to install NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX to /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX
  • 11:57:19 INFO: Flash Xavier A+B in parallel: [ Disk Avail:133.36 GB ]
  • 11:57:19 INFO: Flash Xavier A+B in parallel: Using GenericInstaller to Install NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP
  • 11:57:19 INFO: Flash Xavier A+B in parallel: change working directory to /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DRIVEOS
  • 11:57:19 INFO: Flash Xavier A+B in parallel: [ Component PreInstall Started ]
  • 11:57:19 INFO: Flash Xavier A+B in parallel: current working directory is /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DRIVEOS
  • 11:57:19 INFO: Flash Xavier A+B in parallel: exec_command: sudo /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DriveSW_Components/DrivePlatform/tools/targetfs_passwd.sh /media/j0116030/Others/Nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DRIVEOS {{TARGET_PASSWORD}}
  • 11:57:19 INFO: Flash Xavier A+B in parallel: [host] [sudo] password for j0116030:
  • 11:57:19 INFO: Flash Xavier A+B in parallel:
  • 11:57:23 INFO: Flash Xavier A+B in parallel: [ Component PreInstall Finished with Error ]
  • 11:57:23 INFO: Flash Xavier A+B in parallel: [ 164.00 KB used. Disk Avail: 133.36 GB ]
  • 11:57:23 INFO: Flash Xavier A+B in parallel: [ NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP Install took 3s ]
  • 11:57:23 INFO: Flash Xavier A+B in parallel:
  • 11:57:23 INFO: Flash Xavier A+B in parallel:
  • 11:57:23 SUMMARY: Flash Xavier A+B in parallel: Failed to execute commands with GenericInstaller

Dear @Liang_Qi,
Could you please attach flashing logs (~/.nvsdkm/sdkm.log and ~/.nvsdkm/logs) for more insights about the issue.

This is the logs. Thanks. @SivaRamaKrishnaNV
nvsdkm_logs.zip (612.8 KB)

Dear @Liang_Qi,
I still see the error is same and related to docker as @shayNV pointed. It does not look like issue with board or sdkmanager. Could you check flashing from another host and confirm?

Dear @SivaRamaKrishnaNV,
Thanks for your reply, but I don’t have another host with ubuntu18.
Would you tell me where the problem of docker is? I think it’s also the proxy problem.

Hi @Liang_Qi,

the problem of the docker is at the first action being executed “apt-get update”
You are probable right, and the root cause is probably related to the proxy server setting you are using.
please do not try and change the docker file that sdk manager is using - this is not the right way to solve your issue.

please read this and try to make all the dockers use the proxy settings to access the external network:

after that please try uninstall and reinstall Drive Software 10, and update on the status.

to verify that any docker can access the external network try building a simple docker by executing a simple command like: “docker build .” with a docker file containing this:

FROM ubuntu:18.04
RUN apt-get update

Thanks @shayNV
I wil try this later.

This proxy settings works for my case. Thank you so much!