-
Notifications
You must be signed in to change notification settings - Fork 272
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
Public GPG key error #258
Comments
Seeing the exact issue as well. |
Also seeing this issue and trying to debug it now. |
@klueska I'm starting from the tensorflow/tensorflow:2.7.0-gpu image, I tried following this blog and so I added the following lines at the start of my file (after FROM tensorflow...) RUN apt-get install -y --no-install-recommends wget When running apt-get update, I have the following error :
In order to add as much information as possible, here is the content of the /etc/apt/sources.list.d folder :
I tried deleting both these files before running the previous lines, then I get the following error :
|
I have the exact same issue. Added this to my Dockerfile: And then, when running apt update and apt install:
|
Same here, someone pushed the wrong button at NVIDIA. |
I rotated my keys, but still getting errors. Commands in
Error:
|
It's pretty disappointing that hardly a day's notice is considered enough warning before breaking everyone's ability to install. |
Argggg, borked build club member signin this seems to work for me |
it seems the keys changed today. wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/cuda-ubuntu2004.pin |
This is what I used in the Dockerfile to fix this
|
This worked for me for a dockerfile, I used the alternative approach on the official notice but I had to remove old source files and I also needed to fetch 2 keys, one for "cuda" and one for "machine learning"
Make sure you change |
I can confirm. This is also the line that I needed to add to get it to work. Only the alternative method from the official announcement seems to work in a Docker build. This is what I added at the start of my Dockerfile: (after FROM)
I still think it's strange for NVIDIA to break everyone's build pipelines with only a few hours notice. |
Same here, ubuntu2004 repo is broken because the previous key |
This worked for me, but remember to change the arguments of the command depending on the version of your distribution. Thanks! |
This may solved for me (base image: nvidia/cuda:11.3.1-cudnn8-devel-ubuntu20.04) RUN \
# Update nvidia GPG key
rm /etc/apt/sources.list.d/cuda.list && \
rm /etc/apt/sources.list.d/nvidia-ml.list && \
apt-key del 7fa2af80 && \
apt-get update && apt-get install -y --no-install-recommends wget && \
wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/cuda-keyring_1.0-1_all.deb && \
dpkg -i cuda-keyring_1.0-1_all.deb && \
apt-get update |
This one worked for me here
|
This solved it for me. Thanks! |
It works for me. Thank you! The files |
Context: https://github.com/NVIDIA/nvidia-docker/issues/1631 The next `deeplearning-platform-release/tf2-gpu.2-6` should remove the need for this workaround. http://b/230864778
Context: https://github.com/NVIDIA/nvidia-docker/issues/1631 The next `deeplearning-platform-release/tf2-gpu.2-6` should remove the need for this workaround. http://b/230864778
Same Issue,
Adding this lines above |
In my case I had to comment second line
|
I am getting this error:
|
fix docker container https://github.com/NVIDIA/nvidia-docker/issues/1631
This worked for me. I just had the runtime, so Thank you ❤️ |
I had the same problem building my Docker image with
I just had to delete the old |
- Improved setup.py for different python versions - Fix for broken nvidia dockerfile https://github.com/NVIDIA/nvidia-docker/issues/1631
I had an issue with running Since
I am running Ubuntu 22.02 on x86, so the URLs can be modified with your version and arch accordingly. Note: I did remove all my other cuda-related souces.list.d files before all of this. I am not sure if it's important but I do not think it is. |
Thank you @gauenk but I would like to update for the 3rd step
Adding |
OK |
This manner solves my problem. |
Where's the public GPG key? Was working fine for weeks. Today this error.
The text was updated successfully, but these errors were encountered: