Skip to content

[docs] Document container tunnel enabled by default in Aspire 13.3#772

Draft
aspire-repo-bot[bot] wants to merge 1 commit intorelease/13.3from
docs/container-tunnel-default-13557-f6f34a2fab1a87aa
Draft

[docs] Document container tunnel enabled by default in Aspire 13.3#772
aspire-repo-bot[bot] wants to merge 1 commit intorelease/13.3from
docs/container-tunnel-default-13557-f6f34a2fab1a87aa

Conversation

@aspire-repo-bot
Copy link
Copy Markdown
Contributor

Documents changes from microsoft/aspire#14557

Author: @karolz-ms

Target branch: release/13.3 — chosen based on the source PR milestone 13.3.

Why this PR is needed

PR microsoft/aspire#14557 changed DcpOptions.EnableAspireContainerTunnel from false (opt-in) to true (enabled by default) in Aspire 13.3. This is a significant behavioral change that affects every user running containers, especially those using container runtimes other than Docker Desktop (Docker Engine on Linux, Podman, etc.).

The existing whats-new/aspire-13-3.mdx page had no mention of the container tunnel change. The previous docs (aspire-13.mdx) described the tunnel as an experimental opt-in feature via ASPIRE_ENABLE_CONTAINER_TUNNEL=true. With 13.3, the tunnel is on by default and users may need to know how to opt out.

What was changed

Updated: src/frontend/src/content/docs/whats-new/aspire-13-3.mdx

Added a new section "🔗 Container tunnel enabled by default" that:

  • Explains what the container tunnel is and why it matters
  • Notes that the tunnel was previously opt-in (Aspire 13.0) and is now on by default
  • Documents the ~3–4s startup delay caveat for containers referencing host endpoints
  • Shows how to disable the tunnel via ASPIRE_ENABLE_CONTAINER_TUNNEL=false (both shell and launchSettings.json examples)
  • Links to the inner-loop networking overview for further reading

Also updated the page description frontmatter to mention the container tunnel change.

Files modified

  • src/frontend/src/content/docs/whats-new/aspire-13-3.mdx (updated)

Note: This draft PR needs human review before merging. In particular, verify the startup delay number (~3–4s) is still accurate and whether any additional migration notes are needed for users coming from Docker Desktop-only setups.

Generated by PR Documentation Check · ● 1.4M ·

Add a new section to the What's new in Aspire 13.3 page describing
the container tunnel being enabled by default (aspire/aspire#14557).

- Explains what the tunnel is and why it matters
- Notes the ~3-4s startup delay for containers using host endpoints
- Shows how to opt out via ASPIRE_ENABLE_CONTAINER_TUNNEL=false

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@aspire-repo-bot aspire-repo-bot Bot added the docs-from-code Copilot initiated issue from dotnet/aspire repo label Apr 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-from-code Copilot initiated issue from dotnet/aspire repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants