I’ve been updating some of our droplets to 22.04 and came across this issue where it mentions: NO_PUBKEY 77B79B3FFAF7EF65. This occurs when I either try to apt update or do-release-upgrade.
I’ve tried some solutions like below and searched around, but realized that the key does not exist: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 77B79B3FFAF7EF65
I assume sks-keyservers.net would’ve worked, but it’s down now and keyserver.ubuntu.com does not have the missing key 77B79B3FFAF7EF65.
Is there a quick solution to this? Since I’ll have to apply the method to multiple droplets.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
Enter your email to get $200 in credit for your first 60 days with DigitalOcean.
I also stumbled across this issue when running a simple
sudo apt-get updateon a 20.04 droplet seems like DO updated the do-agent apt gpg key on the 5th december. you can see the new one here: https://repos.insights.digitalocean.com/sonar-agent.asc and the old one they have as a backup: https://repos.insights.digitalocean.com/sonar-agent.asc.bkup
i solved this with:
wget -qO - https://repos.insights.digitalocean.com/sonar-agent.asc | sudo apt-key add -
its worth noting
apt-key addis depreciated but its a simple one-liner.
I would appreciate some official DO guidance with the best way to update this across all my droplets
I just encounter this problem today when upgrading my ubuntu droplet to 22.04. This thing didn’t happened when I upgraded another droplet to 22.04. Found out there are two keys for DO instead of one.
I exported both of keys using:
Edit /etc/apt/sources.list.d/digitalocean-agent.list to this:
Run apt update, the warning should be gone. Then you can safely delete the keys
I’m experiencing the exact same issue. Can’t seem to be able to find a solution anywhere.