I've built my container multiple times this evening, all built fine, and this just now started failing, nothing's changed.
Get:1 https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease [4003 B]
Get:2 https://packages.microsoft.com/ubuntu/18.04/prod bionic/main amd64 Packages [156 kB]
Err:2 https://packages.microsoft.com/ubuntu/18.04/prod bionic/main amd64 Packages
File has unexpected size (156011 != 155826). Mirror sync in progress? [IP: 40.118.250.56 443]
Hashes of expected file:
Thanks for reporting this--I've moved the issue to dotnet/core for slightly more visibility while we work on getting it fixed.
Note to others: I've confirmed this error shows up for me too on a fresh Docker container. After setting up the Ubuntu 18.04 feed based on https://docs.microsoft.com/en-us/dotnet/core/install/linux-ubuntu#1804- and running apt update, it shows up. This is affecting the entire feed, not just .NET packages.
/cc @rbhanda @NikolaMilosavljevic
For our own reference (internal link, sorry), the incident ticket is here: https://portal.microsofticm.com/imp/v3/incidents/details/209631783/home. (Thanks @rbhanda for filing it. 馃檪)
As per our team there is a service updating repos. It should be resolved once that is done. Meanwhile I am following up on this issue and keep everyone updated with changes.
I have to ask @dagood, I've seen this problem several times, and you always fix it or bring it to the right people 馃檹. But could the team maybe review its tests or something so we see less of this size mismatch problem in the future? Again, thanks for the great communication!
Thanks for the kind words. 馃槃 There's some more info about our communication with the team that hosts packages.microsoft.com to help them improve the reliability of the service at https://github.com/dotnet/core/issues/4167, which is slow but still ongoing. They deployed some improvements earlier this year which has seemed to make release-day outages happen less often (we used to have one basically every time we published a servicing release), so we'll be interested to hear what happened this time.
The services are now restored, the issue should be resolved now.
Works here as well, thanks!
Closing this since the issue is resolved.
Most helpful comment
Thanks for reporting this--I've moved the issue to dotnet/core for slightly more visibility while we work on getting it fixed.
Note to others: I've confirmed this error shows up for me too on a fresh Docker container. After setting up the Ubuntu 18.04 feed based on https://docs.microsoft.com/en-us/dotnet/core/install/linux-ubuntu#1804- and running
apt update, it shows up. This is affecting the entire feed, not just .NET packages./cc @rbhanda @NikolaMilosavljevic
For our own reference (internal link, sorry), the incident ticket is here: https://portal.microsofticm.com/imp/v3/incidents/details/209631783/home. (Thanks @rbhanda for filing it. 馃檪)