Containers sometimes go into `FailedToStart` state when all containers are started at the same time.

[JamesNK]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I have an resource command that tells all DCP resources to start at the same time. When I run this command, usually one or more containers become stuck in a FailedToStart state:

Clicking start on the failed containers will let them successfully start on their own.

DCP logs:
dcp-90044718982000-36604.zip

Expected Behavior

All containers start successfully.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version info

No response

Anything else?

No response

[JamesNK]

Branch with "stop all" and "start all" commands: https://github.com/dotnet/aspire/tree/jamesnk/start-all-command

[danegsta]

This should be fixed with the latest DCP insertion