-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WebToolsE2E][Aspire] Deploying Aspire-Samples/Metrics solution using 'azd up', the status of container app shows failed: ContainerCrashing #3321
Comments
@vhvb1989 can you try this? |
I don’t think this is a new problem. We don’t have a way to represent volumes in the manifest and this sample relies on them |
This issue also reproduce on samples\AspireWithDapr.sln solution. |
@v-sherryfan can you paste the output of streaming logs here? |
@davidfowl The log stream is as below, Is this what you want? 2024-02-21T10:01:44.10957 Connecting to the container 'webfrontend'... 2024-02-21T10:01:44.13786 Successfully Connected to container: 'webfrontend' [Revision: 'webfrontend--p5ywlwb-7c6b8ccf77-lwln2', Replica: 'webfrontend--p5ywlwb'] |
The issue was initially filed for @vhvb1989 can you try to reproduce the |
The sample from https://github.com/dotnet/aspire-samples/tree/main/samples/AspireWithDapr might be out of date for preview4. The code and API looks different from the one at https://github.com/dotnet/aspire/tree/main/playground/dapr @philliphoff , are you keeping both samples? Do you know which one is the right one? Should we keep just one? |
Root caused to: dapr/dotnet-sdk#1235 There is a workaround to use version |
@v-cazhang for any future Let's avoid combining issues from different samples. The |
Got it, we will open separate issue for any |
This issue is not reproduced on Aspire 8.0 P3 and 8.0 P4 after updating 'Dapr.AspNetCore' version to 1.13.0-rc03. |
REGRESSION INFO: Also repro on Aspire 8.0.0-preview.2.23619.3
INSTALL STEPS
REPRO STEPS
ACTUAL:
The status shows failed: Failed:appContainerCrashing:
EXPECTED
No issues
The text was updated successfully, but these errors were encountered: