microsoft / microsoft/vscode-azurecontainerapps
Deployment features when Docker is installed locally
Open
Nobody has claimed this yet.
feature
P1
- Dominant language
- TypeScript
- Stars
- 42
- Forks
- 21
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
If Docker is installed locally, it can add some complexity to the deployment process. Using this issue to discuss various points.
- Should we support building an image locally instead of building in ACR? This might be needed to push to other registries.
- Should we support selecting a local image to deploy? This would be similar to or leverage the Docker extension command for pushing an image.
- If an image is local, there might be more info that can be inferred, such as the app's target port. Might be able to infer from the EXPOSE metadata in the image.
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
The issue names no files, tests, or entry points. Start by mapping the deployment flow and its existing Azure Container Registry and Docker extension integration, then resolve whether local image builds, local image selection, and EXPOSE-based port inference are in scope. Done requires agreed behavior for these deployment cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, docker, typescript, vscode
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100