You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All container versions on DockerHub should be updated because the apt repository key for the ROCm apt package sources is outdated.
This requires pulling the new keys by hand.
Because of the key mismatch, it is not possible in old containers to install additional rocm software, therefore many community CI's requires an update to integrate the key update into their CI scripts. e.g. our software alpaka, PIConGPU
$ docker run -it rocm/dev-ubuntu-20.04:4.1
$ apt update
...
[6319 B]
Get:19 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages [2668 B]
Reading package lists... Done
W: GPG error: https://repo.radeon.com/rocm/apt/4.1 xenial InRelease: The following signatures were invalid: EXPKEYSIG 9386B48A1A693C5C James Adrian Edwards (ROCm Release Manager) <[email protected]>
E: The repository 'https://repo.radeon.com/rocm/apt/4.1 xenial 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.
The text was updated successfully, but these errors were encountered:
All container versions on DockerHub should be updated because the apt repository key for the ROCm
apt
package sources is outdated.This requires pulling the new keys by hand.
Because of the key mismatch, it is not possible in old containers to install additional rocm software, therefore many community CI's requires an update to integrate the key update into their CI scripts. e.g. our software alpaka, PIConGPU
Reproducer:
The text was updated successfully, but these errors were encountered: