Debian 11 failed apt update
Do you have any workaround for the following problem?
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
root@139-162-71-30:~# apt update
Hit:1 http://mirrors.linode.com/debian bullseye InRelease
Hit:2 http://mirrors.linode.com/debian-security bullseye-security/updates InRelease
Hit:3 http://mirrors.linode.com/debian bullseye-updates InRelease
Hit:5 https://apt.releases.hashicorp.com bullseye InRelease
Get:4 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [8,993 B]
Err:4 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
Reading package lists… Done
W: GPG error: https://packages.cloud.google.com/apt kubernetes-xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
E: The repository 'https://apt.kubernetes.io kubernetes-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 following command did not help:
gpg --keyserver keyserver.ubuntu.com --recv-key B53DC80D13EDEF05
3 Replies
hdiep
Linode Staff
✓ Best Answer
I wasn't able to replicate this myself with my Debian 11 Linode, but according to Google, this is a known issue when attempting to update their packages on Debian/Ubuntu VMs. I was able to find a few resources online that encountered the same error message you've provided that you might find useful. These other users were able to resolve it by updating the signature keys:
Ubuntu kubernetes-xenial public key is not available: NO_PUBKEY B53DC80D13EDEF05
kubernetes - apt-get update error related with kubeadm - Stack Overflow
Hopefully, these resources point you in the right direction!
