Restore fails on linux for Aspire.Hosting.Orchestration.linux-x64

[GabschD]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I'm trying to build an aspire project in an Azure DevOps pipeline (self hosted on a VMSS with ubuntu 22-04) and it fails on restore.
I found a similar issue, but it mentions 8.2 so maybe its a diffferent one.

Failed to download package 'Aspire.Hosting.Orchestration.linux-x64.9.0.0' from 'https://api.nuget.org/v3-flatcontainer/aspire.hosting.orchestration.linux-x64/9.0.0/aspire.hosting.orchestration.linux-x64.9.0.0.nupkg'.
         The download of 'https://api.nuget.org/v3-flatcontainer/aspire.hosting.orchestration.linux-x64/9.0.0/aspire.hosting.orchestration.linux-x64.9.0.0.nupkg' timed out because no data was received for 60000ms.
           The operation has timed out.

As those links are actually empty.

Csproj for reference:

<Project Sdk="Microsoft.NET.Sdk">
  <Sdk Name="Aspire.AppHost.Sdk" Version="9.0.0" />
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net9.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
    <IsAspireHost>true</IsAspireHost>
    <UserSecretsId>...</UserSecretsId>
  </PropertyGroup>
  <ItemGroup>
    <ProjectReference Include="....Service.csproj" />
  </ItemGroup>
  <ItemGroup>
    <PackageReference Include="Aspire.Hosting.AppHost" Version="9.0.0" />
  </ItemGroup>
</Project>

Expected Behavior

Packages get restored without issues

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version info

dotnet 9.0.0

Anything else?

No response

[GabschD]

I also found #5486 and the workaround seams to work. Only the issue is closed.

[davidfowl]

cc @joperezr

[joperezr]

Thanks for your report @GabschD . By looking at the original error message, seems like this was just a timeout on NuGet, perhaps there was something wrong with the service or network when you tried to run your build? Can you repro this still? Also, can you share what is the workaround that seemed to fix it for you?