![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 51%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMN%3C/text%3E%3C/svg%3E)
522 questions
Hi Mike Navin that's a classic ubuntu package mirror hiccup )) happens to the best of us. any way, thanks for posting this with all the deets makes it way easier to help u out, really, u cant imagine how many ppl review each issue...
any way lets back to u situation, those 403 forbidden errors from archive.ubuntu.com usually mean the mirror u're hitting is either overloaded or temporarily down. good news is, microsoft's hosted agents already have a fix for this baked in, u just gotta tweak ur dockerfile a bit. Aha.
what we wanna do with it, lets switch to security.ubuntu.com it's way more reliable for package fetching. add this line before any apt-get installs in ur dockerfile
RUN sed -i 's|http://archive.ubuntu.com|http://security.ubuntu.com|g' /etc/apt/sources.list
this swaps out the flaky mirror for the more stable one. microsoft docs actually recommend this for hosted agents when ubuntu mirrors act up (source). always run apt-get update first even if u already have it (I do it :))) , sometimes cache gets weird. do this right after the sed command
RUN apt-get update -y --fix-missing
the --fix-missing flag helps if some packages failed earlier. retry logic if u wanna go extra safe, wrap the install in a retry loop. like this
RUN for i in {1..3}; do apt-get install -y libgdiplus libc6-dev && break || sleep 15; done
this tries 3 times with 15-second breaks between fails. saved my builds more than once ))
also if u're using mcr.microsoft.com/dotnet/sdk:8.0-noble, check if u can use a tagged version instead of sha256 hash. time to time the hash points to an image that’s mid-update and causes these issues. give this a shot and lemme know if the errors stick around.
microsoft’s ubuntu agents are usually solid, but mirrors gonna mirror )))
btw, if u still hit snags, u can force-clear the docker build cache in azure pipelines by adding a "docker system prune -af" step just sayin’ :)))) dont give up )))
Best regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment