This is a serious issue nonetheless. I have the same issue after a squeaky clean install with a brand new 22.04 host and just running “apt update && apt upgrade” after the flash. Which I had to do because otherwise it wouldn’t even let me compile a driver for my EDIMAX wireless LAN adapter.
In the Nvidia link above (“Apt upgrade problem: Errors were encountered…”) Nvidia says that this isn’t an error message but a warning, but there are some practical problems:
If anybody tries to install Docker using the standard convenience script (" curl | sh && sudo systemctl --now enable docker") they will crash and burn because the script will abort any “apt install” command because of the error in the opening post (“E: Sub-process /usr/bin/dpkg returned an error code (1)`”, even if it’s supposed to be a warning.
Now Nvidia says “FYI, you won’t see such failure by moving to r32.5 or later L4T release versions”, but we’re now on 36.4 with JP 6.1 and it still has not been fixed.
Not sure if there’s anything the Seeed engineers can do there or we’ll have to wait for the custom 6.2 version. Until then we’ll have to install Docker manually or at least with a substantially modified script. Not good when you have dozens of IPCs.