The problem with using the PC as router in your case is that the network will send out a request which both the router and the PC see…both will try to answer. So it probably isn’t a good idea to use host PC as router when you can’t control the router appliance itself. If you do choose this it is just a button press in JetPack when it asks which method to use.
I don’t know what you have using docker. It is quite possible this is confusing networking, but I have no way to advise on it. Someone who knows docker better might be able to tell you how to trace whatever is actually creating or using the docker network interface.
There is a good chance that docker setup is altering things, though it might have nothing to do with it. I see an address your host is failing to reach is IPv6 format (usually it is IPv4 format…sometimes a lack of IPv6 features can interfere) “2001:67c:1360:8001:22” for “ports.ubuntu.com”. Can you provide what you see from these commands without rebooting or configuring anything between commands:
Keep in mind that it isn’t always a problem on the PC when there is a network issue, e.g., if you request a package which doesn’t exist you’ll see an error, but there are often multiple mirror servers and it would fail over.
The part which is more likely to be of interest is where the picture shows:
Error: CUDA cannot be installed on device. ...
cuda-toolkit-9-0 libgomp1 libfreeimage-dev libopenmpi-dev openmpi-bin
After these packages are installed on device, press Enter key to continue
If you look at your JetPack directory you should see a “jetpack_download/” subdirectory. Within this what do you see from:
If you see that file, and it is “arm64.deb”, then this file is for install on the Jetson. You could try to manually copy this to the Jetson and run:
sudo dpkg -i
# ...if that succeeded, then also:
sudo apt-get install -f
If you see an “amd64.deb” file, then this is for your host instead, but that’s a different topic.
Note that the repo package adds a set of “.deb” files to a subdirectory of “/var” and then tells apt to treat this the same as a repo somewhere on the internet. Those files become available for automatic dependency resolving when you use apt. Without this repo you won’t be able to succeed. So probably the first thing to do is figure out if this repo .deb can be installed, or figure out why it is failing. After that branch off to fix other issues.
Any time you are getting any message about there already be an apt or dpkg operation running and that it can’t do this at the same time see what the result is from:
sudo lsof /var/lib/dpkg/lock
(note whether such error is from trying to install arm64 versus amd64 files…arm64 is Jetson, amd64 is host…you want to check lsof of the lock file on the machine which is failing)