When you run aspire deploy in a scenario where your container runtime is not running, the failure mode is a bit strange because we end up issuing a cancellation to the provisioning context step that is running concurrently. This makes it harder to see the root cause from the view.
09:38:32 (build-container-images) ✗ [ERR] Container runtime is not running or is unhealthy. Cannot build container images.
09:38:32 (build-images) ✗ Docker is not running or is unhealthy. (0.0s)
09:38:32 (build-images) ✗ Building container images failed
09:38:32 (build-container-images) ✗ Step 'build-container-images' failed: Container runtime is not running or is unhealthy.
09:38:32 (create-provisioning-context) ✗ Step 'create-provisioning-context' failed: DefaultAzureCredential failed to retrieve a token from the included credentials. See the troubleshooting guide for more information.
https://aka.ms/azsdk/net/identity/defaultazurecredential/troubleshoot
09:38:32 (create-provisioning-context) ✗ - EnvironmentCredential authentication unavailable. Environment variables are not fully configured. See the troubleshooting guide for more information.
https://aka.ms/azsdk/net/identity/environmentcredential/troubleshoot
09:38:32 (create-provisioning-context) ✗ - VisualStudioCredential authentication failed: Visual Studio Token provider can't be accessed at /Users/captainsafia/.IdentityService/AzureServiceAuth/tokenprovider.json
09:38:32 (create-provisioning-context) ✗ - VisualStudioCodeCredential requires the Azure.Identity.Broker package to be referenced from the project. VS Code Azure See the troubleshooting guide for more information.
https://aka.ms/azsdk/net/identity/vscodecredential/troubleshoot
09:38:32 (create-provisioning-context) ✗ - AzureCliCredential authentication failed: A task was canceled.
09:38:32 (create-provisioning-context) ✗ - AzureDeveloperCliCredential authentication failed: A task was canceled.
09:38:32 (create-provisioning-context) ✗ - The BrokerCredential requires the Azure.Identity.Broker package to be referenced. See the troubleshooting guide for more information. https://aka.ms/azsdk/net/identity/brokercredential/troubleshoot
When you run
aspire deployin a scenario where your container runtime is not running, the failure mode is a bit strange because we end up issuing a cancellation to the provisioning context step that is running concurrently. This makes it harder to see the root cause from the view.