Repository navigation
Update dev container configs to use aspire certs instead of dotnet dev-certs #583
Description
Summary
The dev container configurations in get-started/dev-containers.mdx use dotnet dev-certs https --trust in postStartCommand/postCreateCommand. These should be updated to use aspire certs trust instead.
Locations
src/frontend/src/content/docs/get-started/dev-containers.mdx— 6 instances across multiple devcontainer.json examples
Notes
- The Aspire CLI needs to be available in the dev container image for this to work
- May require updating the dev container feature/image to include the Aspire CLI
aspire-sdk-templates.mdxalso has one instance that should be updated at the same time
Metadata
Metadata
Assignees
Labels
No labels
Activity
IEvangelist commentedon Jun 2, 2026
Triage → David Pine (@IEvangelist)
Cross-cutting change — 6
devcontainer.jsonexamples inget-started/dev-containers.mdxplus the implications:aspire certs trustis the polyglot path going forward; we should also explain the relationship withdotnet dev-certsfor users who don't have the CLI.onCreateCommandfirst.Worth a quick design pass before handing to Copilot, otherwise we risk publishing devcontainers that fail to start cleanly.
IEvangelist commentedon Oct 18, 2026
Addressed by #1667. The content is now on
main, so closing.