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.
apt-get update --allow-releaseinfo-change
Ign:1 cdrom://[Debian GNU/Linux 10.2.0 _Buster_ - Official amd64 DVD Binary-1 20191116-09:57] buster InRelease
Err:2 cdrom://[Debian GNU/Linux 10.2.0 _Buster_ - Official amd64 DVD Binary-1 20191116-09:57] buster Release
Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
Hit:3 http://nginx.org/packages/debian buster InRelease
Get:4 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:5 http://security.debian.org/debian-security buster/updates/main Sources [93.4 kB]
Get:6 http://security.debian.org/debian-security buster/updates/main amd64 Packages [162 kB]
Get:7 http://security.debian.org/debian-security buster/updates/main Translation-en [83.6 kB]
Hit:8 http://deb.debian.org/debian buster InRelease
Get:9 http://deb.debian.org/debian buster-updates InRelease [49.3 kB]
Reading package lists... Done
E: The repository 'cdrom://[Debian GNU/Linux 10.2.0 _Buster_ - Official amd64 DVD Binary-1 20191116-09:57] 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.
and when i run the curl -sSL https://install.pi-hole.net |bash
this keeps failing.
[✓] Disk space check
[✗] Update local cache of available packages
Error: Unable to update package cache. Please try "apt-get update"root@go-doh:~#
This question was answered by @CanadaGuy:
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.
Click below to sign up and get $100 of credit to try our products over 60 days!
this is freally very informative post, thanks for the nice update
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.