microsoft / microsoft/aspire.dev
[docs] Missing information about the dotnet container steps around image being built locally
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 193
- Forks
- 87
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 73
Description
Issue:
- The dotnet container step performs a local build of the image that is to be used by the aspire CLI - in this case aspire deploy. However the fact that this local step happens is not reflected on our documentation.
- This can lead to people having Docker Containers on Windows locally, and therefore any Linux image is likely to fail to build locally.
ASK:
- Clarify in our CLI documentation that the local containers must be exactly the same OS as the image that is defined in the AppHost.
Contributor guide
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 CLI documentation and find the section describing the dotnet container step used by the Aspire CLI, including aspire deploy. Explain that the image is built locally and that local containers must use the same OS as the image defined in the AppHost; done means this constraint is clear to Windows users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100