Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ROCm container on Dockerhub using outdated keys #83

Open
psychocoderHPC opened this issue Aug 10, 2021 · 0 comments
Open

ROCm container on Dockerhub using outdated keys #83

psychocoderHPC opened this issue Aug 10, 2021 · 0 comments

Comments

@psychocoderHPC
Copy link

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

wget -q -O - https://repo.radeon.com/rocm/rocm.gpg.key | sudo apt-key add -
apt-get -y --quiet update

Reproducer:

$ 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant