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

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05 #14

Open
dyrnq opened this issue Jan 29, 2023 · 2 comments

Comments

@dyrnq
Copy link
Owner

dyrnq commented Jan 29, 2023

apt update

Err:4 https://mirrors.tencent.com/kubernetes/apt kubernetes-xenial InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://mirrors.tencent.com/kubernetes/apt kubernetes-xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
W: Failed to fetch https://mirrors.tencent.com/kubernetes/apt/dists/kubernetes-xenial/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
W: Some index files failed to download. They have been ignored, or old ones used instead.
apt update

Err:6 https://mirrors.aliyun.com/kubernetes/apt kubernetes-xenial InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
@dyrnq
Copy link
Owner Author

dyrnq commented Jan 29, 2023

xref kubernetes/release#1982

@bigbigbighead
Copy link

hey,bro. I just met the same problem as you. Even the pubkey is the same. How did you solve it?

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

2 participants