RUN (all capitals) is typically the way the docker run command is written. Depending on the state during the container build the command could be executed as root or another user.
Sorry for the noob-question (I am a mechanical engeneer in numerical analysis’ - the craft of computer science is not native to me). I don’t know where to execute the code. I am building the singularity container from a singularity *.def. When is docker available in the building process of singularity?
Do these file names stay the same and their contents change? Wondering if this would work as a long term solution to solve for key rotations. Don’t want to hardcode the filenames and then have this fail in 3 months.
W: GPG error: file:/var/cudnn-local-repo-ubuntu2204-8.8.0.121 InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BE5F80F804B81517
E: The repository 'file:/var/cudnn-local-repo-ubuntu2204-8.8.0.121 InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: file:/var/cudnn-local-repo-ubuntu2204-8.9.3.28 InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 619ECF317F7A158C
E: The repository 'file:/var/cudnn-local-repo-ubuntu2204-8.9.3.28 InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: file:/var/nv-tensorrt-local-repo-ubuntu2204-8.5.3-cuda-11.8 InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D129ACC63E951519
E: The repository 'file:/var/nv-tensorrt-local-repo-ubuntu2204-8.5.3-cuda-11.8 InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: file:/var/nv-tensorrt-local-repo-ubuntu2204-8.6.1-cuda-11.8 InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F981A7F10628887B
E: The repository 'file:/var/nv-tensorrt-local-repo-ubuntu2204-8.6.1-cuda-11.8 InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
I had same issue while installing Cuda on my Jetson agx xavier by referencing [this]
1. error explanation
when I doing this I got an error:
jetsonagx@jetsonagx-desktop:~/Downloads/nvidia/sdkm_downloads$ sudo dpkg -i cuda-repo-l4t-11-4-local_11.4.19-1_arm64.deb
Selecting previously unselected package cuda-repo-l4t-11-4-local.
(Reading database ... 148565 files and directories currently installed.)
Preparing to unpack cuda-repo-l4t-11-4-local_11.4.19-1_arm64.deb ...
Unpacking cuda-repo-l4t-11-4-local (11.4.19-1) ...
Setting up cuda-repo-l4t-11-4-local (11.4.19-1) ...
The public cuda-repo-l4t-11-4-local GPG key does not appear to be installed.
To install the key, run this command:
sudo cp /var/cuda-repo-l4t-11-4-local/cuda-13070C62-keyring.gpg /usr/share/keyrings/
jetsonagx@jetsonagx-desktop:~/Downloads/nvidia/sdkm_downloads$ sudo apt-key add /var/cuda-repo-l4t-11-4-local/13070C62.pub
OK
jetsonagx@jetsonagx-desktop:~/Downloads/nvidia/sdkm_downloads$ sudo apt-get -y update
#...
Err:1 file:/var/cuda-repo-l4t-11-4-local InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
#...
Reading package lists... Done
W: GPG error: file:/var/cuda-repo-l4t-11-4-local InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 65E126F113070C62
E: The repository 'file:/var/cuda-repo-l4t-11-4-local InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
I tried everything said in Internet, but didn’t work.
2. issue solving process explanation
What I did is
as displayed in first command:
To install the key, run this command:
sudo cp /var/cuda-repo-l4t-11-4-local/cuda-13070C62-keyring.gpg /usr/share/keyrings/