Question
Why does fresh Debian 10 image fail apt update
Fresh Debian 10 image, running apt update gives repository errors:
Ign:1 http://mirrors.digitalocean.com/ubuntu buster InRelease
Ign:2 http://mirrors.digitalocean.com/ubuntu buster-updates InRelease
Ign:3 http://mirrors.digitalocean.com/ubuntu buster-backports InRelease
Err:4 http://mirrors.digitalocean.com/ubuntu buster Release
404 Not Found [IP: 2606:4700:30::6818:74d1 80]
Err:5 http://mirrors.digitalocean.com/ubuntu buster-updates Release
404 Not Found [IP: 2606:4700:30::6818:74d1 80]
Err:6 http://mirrors.digitalocean.com/ubuntu buster-backports Release
404 Not Found [IP: 2606:4700:30::6818:74d1 80]
Ign:7 http://security.ubuntu.com/ubuntu buster-security InRelease
Err:8 http://security.ubuntu.com/ubuntu buster-security Release
404 Not Found [IP: 2001:67c:1360:8001::17 80]
Reading package lists... Done
E: The repository 'http://mirrors.digitalocean.com/ubuntu buster Release' does not have a Release file.
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.
E: The repository 'http://mirrors.digitalocean.com/ubuntu buster-updates Release' does not have a Release file.
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.
E: The repository 'http://mirrors.digitalocean.com/ubuntu buster-backports Release' does not have a Release file.
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.
E: The repository 'http://security.ubuntu.com/ubuntu buster-security Release' does not have a Release file.
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.
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.
×
I just tried a new Droplet from scratch and it seems to work fine. The above error resulted from a droplet that was originally Ubuntu 18.04, but rebuilt with Debian 10.
this is freally very informative post, thanks for the nice update