Aspire fails to start after upgrading to Preview 4

[MatinTheGC]

I was using Aspire Preview 3 and it was working fine. But after I upgraded it to Preview 4, I now get this error when I try to run my app:

C:\Users\**\AppData\Local\JetBrains\Installations\Rider233\plugins\dpa\DotFiles\JetBrains.DPA.Runner.exe --handle=21916 --backend-pid=2476 --etw-collect-flags=67108622 --detach-event-name=dpa.detach.21916 C:/Source/Bargeh/Source/Build/Bargeh.Aspire.AppHost/bin/Debug/net8.0/Bargeh.Aspire.AppHost.exe
info: Aspire.Hosting.DistributedApplication[0]
      Aspire version: 8.0.0-preview.4.24156.9+692dc41a65da572a7df25d53a9f2880afe59fdd8
info: Aspire.Hosting.DistributedApplication[0]
      Distributed application starting.
info: Aspire.Hosting.DistributedApplication[0]
      Application host directory is: C:\Source\Bargeh\Source\Build\Bargeh.Aspire.AppHost
Application orchestrator dependency check had an unexpected error System.InvalidOperationException: Command C:\Program Files\dotnet\packs\Aspire.Hosting.Orchestration.win-x64\8.0.0-preview.3.24105.21\tools\dcp.exe info returned non-zero exit code 1
   at Aspire.Hosting.Dcp.DcpDependencyCheck.EnsureDcpDependenciesAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/DcpDependencyCheck.cs:line 67.

Process finished with exit code 129.

[MatinTheGC]

I was able to solve this problem by running this command:

dotnet workload update

The problem was that the package was up to date, but the workload wasn't.

[smbecker]

I'm still running into this issue even after a workload update

dotnet workload list

Installed Workload Id      Manifest Version                     Installation Source
-----------------------------------------------------------------------------------
aspire                     8.0.0-preview.4.24156.9/8.0.100      SDK 8.0.200

Use `dotnet workload search` to find additional workloads to install.

Output when running application...

info: Aspire.Hosting.DistributedApplication[0]
      Aspire version: 8.0.0-preview.4.24156.9+692dc41a65da572a7df25d53a9f2880afe59fdd8
info: Aspire.Hosting.DistributedApplication[0]
      Distributed application starting.
info: Aspire.Hosting.DistributedApplication[0]
      Application host directory is: /.../src/Hosting/AppHost
^CApplication orchestrator dependency check had an unexpected error System.Threading.Tasks.TaskCanceledException: A task was canceled.
   at Aspire.Hosting.Dcp.DcpDependencyCheck.EnsureDcpDependenciesAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/DcpDependencyCheck.cs:line 67.

[davidfowl]

Can you look at this comment #2871 (comment) and see if it works for you.

Specifically

docker system df was taking quite a long time (1-2 minutes) but I performed a docker system prune -a and cleaned out a bunch of old containers and volumes that I no longer needed. Once I did that, it was back to running really quickly. Now the tooling starts up as expected. It seems the issue was the long execution time for docker system df.

[davidfowl]

Oh wait @smbecker did that not work for you?

[smbecker]

Oh wait @smbecker did that not work for you?

Yes it did

[thomastmhuynh]

I have the same problem too,
I installed the Aspire Hosting package via NuGet on VisualStudio (8.0.0-preview.4.24156.9) and the workload is updated to 8.0.0-preview.4.24156.9/8.0.100
I also prune the docker system too

[smbecker]

I have the same problem too, I installed the Aspire Hosting package via NuGet on VisualStudio (8.0.0-preview.4.24156.9) and the workload is updated to 8.0.0-preview.4.24156.9/8.0.100 I also prune the docker system too

@minhthien280 How long does docker system df take on your system? You may need to clean up some of the containers, images, and/or volumes.

[thomastmhuynh]

Seem like I'm just being stupid and not checking whether docker desktop is running.

[niclascoeli]

I had the same issue when attempting to update from preview 3 to 4. At that time I just ignored it and remained on preview 3. However now I had the same issue on preview 5 and managed to figure out that the issue stemmed from the workload failing to update and somehow the old version remained the default, even when saying it did update successfully.

I would get the above message every time i ran the update command.

I resolved it by:

• Uninstalling the workload - dotnet workload uninstall aspire
• Manually cleaning everything related to Aspire in C:\Program Files\dotnet\packs (i gotten multiple versions there)
• Restarting the computer
• Once again installing the Aspire workload - dotnet workload install aspire

[davidfowl]

The workloads are gone and it's just nuget now! Update to Aspire 9.x (2 at time of writing).