Why does fresh Debian 10 image fail apt update

November 14, 2019 394 views
Debian 10

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.
2 comments
1 Answer

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.

View the original comment

  • Can there perhaps be an explanation of why this happens? I figured “rebuild” would allow switching OS so that IP address is maintained. Is that not possible?

    edited by bobbyiliev
    • Hello @CanadaGuy,

      According to the official documentation here at this time, rebuilding a Droplet to a different base OS distribution can cause issues and is not recommended. Instead, you should create a new Droplet using your chosen distribution and migrate to it.

      But from the error that I’m seeing I think that you might have to update your repository list to match the Debian repositories. You could try to check the contents of /etc/apt/sources.lit on your rebuilt droplet and the new Debian droplet and make sure that they match.

      Regards,
      Bobby

Have another answer? Share your knowledge.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!