microsoft / microsoft/vscode-azurecontainerapps
Unclear error message shows when deployment fails due to mismatched TargetPort in “Deploy to Container App with Copilot”
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 42
- Forks
- 21
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
OS: Win 11
Build Version: 20260118.1
Regression: Not a Regression
Repro Steps:
- Right-click a container app and select "Deploy to Container App with Copilot...".
- In the Summary view, note that the default Target Port is set to 80 (while the container listens on 3000).
- Don't change any item and click "Confirm" to start deployment -> Fail to deploy with an error.
- Check whether the error message is clear or not.
Expect:
The deployment failure should surface a clear and actionable error message, such as “The TargetPort 80 does not match the listening port 3000” in Azure portal.
Actual:
The deployment fails with a generic timeout message.
More Info:
This issue also reproduces when executing "Deploy to Container App..." command.
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 by reproducing the failure through “Deploy to Container App with Copilot...” and “Deploy to Container App...” using a container listening on 3000 while Target Port remains 80. Trace the deployment error handling to find where the generic timeout is surfaced. Done means the failure explains the TargetPort mismatch and gives an actionable message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100