microsoft / microsoft/aspire-samples
[WebToolsE2E][Aspire] After successfully deploying the StandaloneDashboard solution, the status of the ca-consoleapp container app is Failed: mainContainerCrashing.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 345
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 30
Description
REGRESSION INFO: Also repro on main + azd 1.8.0
INSTALL STEPS
- Clean machine: Win11 x64 23h2 ENU
- Install VS 17.10 Preview 5 [ Includes Aspire 8.0.0-preview.6.24214.1 ]
- Apply NuGet dotnet-tools Feeds
- Install Docker Desktop for Windows
- Install the latest azd [1.9.0-beta.1-daily.3712265]
REPRO STEPS
- Clone aspire-samples repo, checkout
preview.6branch - Deploy using azd
- Open the samples\StandaloneDashboard solution folder in a Command Prompt
- Runing
azd init, select 'Use code in the current directory' > Confirm and continue initializing my app, type a new environment name, press enter. - Run
azd upto deploy to Azure
- Open the resource group, the ca-consoleapp container apps status is failed:mainContainerCrashing.
ACTUAL:
After deployment successful, go to resource group, the ca-consoleapp container apps status is failed:mainContainerCrashing
EXPECTED
The ca-consoleapp container apps status is successful.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the samples\StandaloneDashboard solution folder and reproduce the deployment with azd init followed by azd up on the preview.6 branch. Inspect the Azure resource group and the ca-consoleapp container app after deployment; done means its status is successful rather than Failed: mainContainerCrashing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, docker
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100