Skip to content

Add container tunnel base image configuration - #20667

Merged
David Negstad (danegsta) merged 5 commits into
mainfrom
danegsta-configure-container-tunnel-image
Oct 2, 2026
Merged

David Negstad (danegsta) merged 5 commits into
mainfrom
danegsta-configure-container-tunnel-image

Conversation

@danegsta

Copy link
Copy Markdown
Member

Description

DCP supports overriding the base image used by the container network tunnel, but Aspire did not expose that setting to AppHost or CLI users. This adds user-facing configuration so environments that require a customized or mirrored base image can configure the tunnel without modifying DCP directly.

Users can set the image through Aspire configuration:

aspire config set containerTunnel.baseImage example.com/aspire-tunnel:configured

The setting is projected to ASPIRE_CONTAINER_TUNNEL_BASE_IMAGE through a reusable AppHost configuration projector. .NET AppHosts receive it in their existing process environment, while polyglot AppHosts receive it through the existing AppHost server-session environment so the value reaches Aspire Hosting and DCP rather than the guest client process.

The AppHost also supports DcpPublisher:ContainerTunnelBaseImage and the --dcp-container-tunnel-base-image argument. Explicit AppHost configuration and existing environment values retain precedence over the Aspire config value.

Validation completed:

  • Aspire CLI configuration, projection, .NET AppHost, and polyglot AppHost tests passed.
  • Aspire Hosting DCP argument and environment binding tests passed.
  • The DCP executor test verifies the configured value is emitted as the tunnel proxy BaseImage.
  • git diff --check passed.

Fixes # (issue)

Checklist

  • Is this feature complete?
    • Yes. Ready to ship.
    • No. Follow-up changes expected.
  • Are you including unit tests for the changes and scenario tests if relevant?
    • Yes
    • No
  • Did you add public API?
    • Yes
      • If yes, did you have an API Review for it?
        • Yes
        • No
      • Did you add <remarks /> and <code /> elements on your triple slash comments?
        • Yes
        • No
    • No
  • Does the change make any security assumptions or guarantees?
    • Yes
      • If yes, have you done a threat model and had a security review?
        • Yes
        • No
    • No

Expose the DCP container tunnel base image through AppHost configuration and aspire config, and project CLI settings into both .NET and polyglot AppHost server environments.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 20667

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 20667"

@github-actions

This comment has been minimized.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

Direct-launch precedence is inverted, and the committed VS Code configuration schema remains stale.

Review effort: Balanced
Findings: 2 Medium severity

Open (2)
What changed in this PR

Adds configurable container-tunnel base images across the CLI, AppHost, and DCP pipeline.

Changes:

  • Adds Aspire config, environment-variable, and AppHost argument support.
  • Projects configuration into .NET and polyglot AppHosts.
  • Passes the configured image to DCP with focused tests.
File Description
tests/​Aspire.Hosting.Tests/​Dcp/​DcpExecutorTests.cs Verifies DCP tunnel image emission.
tests/​Aspire.Hosting.Tests/​Dcp/​DcpCliArgsTests.cs Tests argument and configuration binding.
tests/​Aspire.Cli.Tests/​Utils/​CliTestHelper.cs Registers the projector in tests.
tests/​Aspire.Cli.Tests/​Projects/​GuestAppHostProjectTests.cs Tests polyglot projection.
tests/​Aspire.Cli.Tests/​Projects/​DotNetAppHostProjectTests.cs Tests .NET projection.
tests/​Aspire.Cli.Tests/​Projects/​AppHostConfigurationProjectorTests.cs Tests projection precedence.
tests/​Aspire.Cli.Tests/​Commands/​ConfigCommandTests.cs Tests configuration persistence and discovery.
src/​Shared/​KnownConfigNames.cs Defines the environment variable.
src/​Aspire.Hosting/​DistributedApplicationBuilder.cs Maps the new AppHost argument.
src/​Aspire.Hosting/​Dcp/​DcpOptions.cs Binds the tunnel image option.
src/​Aspire.Hosting/​Dcp/​ContainerNetworkEndpointProvisioner.cs Sends the image to DCP.
src/​Aspire.Cli/​Projects/​GuestAppHostProject.cs Projects configuration into the server session.
src/​Aspire.Cli/​Projects/​DotNetAppHostProject.cs Projects configuration into .NET launches.
src/​Aspire.Cli/​Projects/​AppHostConfigurationProjector.cs Implements reusable projection logic.
src/​Aspire.Cli/​Program.cs Registers the projector service.
src/​Aspire.Cli/​Configuration/​AspireConfigFile.cs Defines containerTunnel.baseImage.

Include the container tunnel base image setting in the committed VS Code schema.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🔵 Needs a closer look

Direct .NET launches currently let the projected default override an explicit launch-profile value.

Review effort: Balanced
Findings: 2 Medium severity

Open (2)

@github-actions

This comment has been minimized.

Project Aspire config into the final launch environment so launch profile values override it consistently across direct and SDK-based AppHost launches.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟢 Approval recommended

The configuration flows correctly through all affected surfaces and has focused regression coverage.

Review effort: Balanced
Findings: 1 Medium severity

Open (1)
Resolved since last review (1)

@github-actions

This comment has been minimized.

@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@github-actions

This comment has been minimized.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟢 Approval recommended

The configuration path, precedence behavior, DCP propagation, generated schema, and relevant tests are complete and consistent.

Review effort: Balanced
Findings: None

Resolved since last review (1)

@danegsta

Copy link
Copy Markdown
Member Author

PR Testing Report

PR Information

Artifact Version Verification

  • Expected Commit: fcd44a30b2e3789a65977d23106736620fc0174d
  • Installed Version: 17.0.0-pr.20667.gfcd44a30
  • Status: ✅ Verified

Changes Analyzed

Files Changed

  • extension/schemas/aspire-config.schema.json
  • src/Aspire.Cli/Configuration/AspireConfigFile.cs
  • src/Aspire.Cli/Program.cs
  • src/Aspire.Cli/Projects/AppHostConfigurationProjector.cs
  • src/Aspire.Cli/Projects/DotNetAppHostProject.cs
  • src/Aspire.Cli/Projects/GuestAppHostProject.cs
  • src/Aspire.Hosting/Dcp/ContainerNetworkEndpointProvisioner.cs
  • src/Aspire.Hosting/Dcp/DcpOptions.cs
  • src/Aspire.Hosting/DistributedApplicationBuilder.cs
  • src/Shared/KnownConfigNames.cs
  • Related CLI and Hosting tests

Change Categories

  • CLI configuration and AppHost launch changes
  • Hosting/DCP resource configuration changes
  • VS Code configuration schema change
  • Test changes
  • Dashboard behavior changes
  • Template behavior changes
  • CI infrastructure changes

Test Scenarios Executed

Scenario 1: Aspire configuration contract

Objective: Verify the new setting can be persisted through aspire config and is advertised by the machine-readable configuration schema.
Coverage Type: Happy path
Status: ✅ Passed

Steps:

  1. Ran aspire config set containerTunnel.baseImage example.com/aspire-tunnel:configured.
  2. Verified the nested value was persisted in aspire.config.json.
  3. Ran aspire config info --json.
  4. Verified containerTunnel.baseImage is described as a string setting.

Evidence:

  • scenario-config/set-output.txt
  • scenario-config/get-output.txt
  • scenario-config/result.txt

Scenario 2: .NET AppHost runtime projection

Objective: Verify project-local Aspire configuration reaches the live DCP ContainerNetworkTunnelProxy resource.
Coverage Type: Happy path
Status: ✅ Passed

Steps:

  1. Created a fresh C# file-based AppHost from the PR hive.
  2. Added a host executable and a container that references the host endpoint, forcing a container-network tunnel.
  3. Configured containerTunnel.baseImage with a test image hosted in a temporary local registry.
  4. Started the AppHost and queried the live DCP API.

Observations:

  • spec.baseImage was localhost:50567/aspire-tunnel:config.
  • The tunnel resource state was Running.

Evidence:

  • scenario-dotnet/tunnel-proxy-spec.json
  • scenario-dotnet/result.txt

Scenario 3: Launch-profile precedence

Objective: Verify a launch-profile ASPIRE_CONTAINER_TUNNEL_BASE_IMAGE value overrides persisted Aspire configuration.
Coverage Type: Precedence boundary
Status: ✅ Passed

Steps:

  1. Kept containerTunnel.baseImage set to the configured test image.
  2. Set ASPIRE_CONTAINER_TUNNEL_BASE_IMAGE to a different image in the AppHost launch profile.
  3. Started the AppHost and queried the live DCP resource.

Observations:

  • spec.baseImage contained the launch-profile image, not the persisted Aspire configuration value.

Evidence:

  • scenario-dotnet/tunnel-precedence-spec.json
  • scenario-dotnet/precedence-result.txt

Scenario 4: Polyglot AppHost-server projection

Objective: Verify a TypeScript guest AppHost projects the setting to the .NET AppHost server that owns Hosting and DCP.
Coverage Type: Architecture boundary
Status: ✅ Passed

Steps:

  1. Created a fresh TypeScript AppHost from the PR hive.
  2. Added the host-executable and tunnel-dependent-container topology.
  3. Built the TypeScript AppHost and configured the custom tunnel image.
  4. Started the AppHost and queried the live DCP API.

Observations:

  • spec.baseImage was localhost:50567/aspire-tunnel:config.
  • The tunnel resource state was Running.

Evidence:

  • scenario-typescript/build-output.txt
  • scenario-typescript/tunnel-proxy-spec.json
  • scenario-typescript/result.txt

Scenario 5: AppHost-relative configuration outside the current directory

Objective: Verify aspire start --apphost <absolute-path> reads configuration relative to the selected AppHost rather than the CLI launch directory.
Coverage Type: Negative/boundary
Status: ✅ Passed after fixing a defect found during testing

Steps:

  1. Created a fresh AppHost with project-local containerTunnel.baseImage.
  2. Launched the original PR artifact from an unrelated repository directory.
  3. Confirmed the live DCP resource omitted spec.baseImage, exposing a real configuration-scope bug.
  4. Updated AppHostConfigurationProjector to use the existing directory-scoped IConfigurationService lookup.
  5. Verified the fix with a locally built CLI.
  6. Installed the refreshed PR artifact at fcd44a30b2 and repeated the scenario from the unrelated directory.

Observations:

  • The refreshed artifact set spec.baseImage to localhost:50567/aspire-tunnel:config.
  • The tunnel resource state was Running.

Evidence:

  • scenario-external-apphost/start-external-cwd-output.txt
  • scenario-external-apphost/start-fixed-source-output.txt
  • scenario-external-apphost/start-refreshed-artifact-output.txt
  • scenario-external-apphost/tunnel-refreshed-artifact.json
  • scenario-external-apphost/refreshed-artifact-result.txt

Scenario 6: Schema regeneration and extension build

Objective: Verify the committed VS Code Aspire configuration schema is generated from the CLI model and the extension still builds.
Coverage Type: Generated artifact/build validation
Status: ✅ Passed

Steps:

  1. Regenerated the Aspire configuration schemas.
  2. Confirmed extension/schemas/aspire-config.schema.json had no diff.
  3. Ran extension/build.sh, which installed the pinned Yarn toolchain, compiled the extension, and built the Aspire CLI.

Evidence:

  • scenario-extension/schema-generation-output.txt
  • scenario-extension/build-output.txt

Source Validation

  • dotnet test --project tests/Aspire.Cli.Tests/Aspire.Cli.Tests.csproj --no-launch-profile -- --filter-class '*.AppHostConfigurationProjectorTests' --filter-class '*.DotNetAppHostProjectTests' --filter-class '*.GuestAppHostProjectTests' --filter-not-trait 'quarantined=true' --filter-not-trait 'outerloop=true'
    • Result: 232 passed, 1 skipped because it requires a case-sensitive filesystem.
  • dotnet build src/Aspire.Cli/Aspire.Cli.csproj --no-restore
    • Result: Passed with 0 warnings and 0 errors.
  • extension/build.sh
    • Result: Passed. Webpack emitted its existing optional-dependency/dynamic-request warnings.
  • Schema regeneration
    • Result: Passed with no committed schema diff.

Exploratory Invalid-Image Check

An unavailable base-image tag was also tried. DCP's derived tunnel-client image uses Docker/BuildKit caching, so the tunnel could be reconstructed from cached layers even after removing the tagged derived image. This did not provide deterministic evidence about image-pull failure behavior and is not counted as a pass or failure for this configuration-wiring PR.

Summary

Scenario Status Notes
Aspire configuration contract ✅ Passed Persisted and advertised in JSON schema
.NET runtime projection ✅ Passed Live DCP resource contained configured image
Launch-profile precedence ✅ Passed Launch profile overrode persisted config
Polyglot server projection ✅ Passed Setting reached the AppHost server
External --apphost configuration ✅ Passed Defect found, fixed, and verified in refreshed PR artifact
Schema regeneration and extension build ✅ Passed Generated schema clean; extension/CLI build passed

Overall Result

✅ PR VERIFIED

The refreshed PR artifact matches the current head commit and all meaningful runtime, precedence, architecture, boundary, schema, and build scenarios passed.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟢 Approval recommended

The configuration flow, precedence rules, runtime projection, DCP integration, and generated schema are consistently implemented and tested.

Review effort: Balanced
Findings: None

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Tests selector

56 / 98 PR test projects · 6 PR jobs, from 18 changed files.

Selected PR test projects (56 / 98)

Aspire.Cli.EndToEnd.Tests, Aspire.Cli.Tests, Aspire.Dashboard.Components.Tests, Aspire.Dashboard.Tests, Aspire.Hosting.Analyzers.Tests, Aspire.Hosting.Azure.Kubernetes.Tests, Aspire.Hosting.Azure.Kusto.Tests, Aspire.Hosting.Azure.Provisioning.Tests, Aspire.Hosting.Azure.Tests, Aspire.Hosting.Blazor.Tests, Aspire.Hosting.Browsers.Tests, Aspire.Hosting.CodeGeneration.Go.Tests, Aspire.Hosting.CodeGeneration.Java.Tests, Aspire.Hosting.CodeGeneration.Python.Tests, Aspire.Hosting.CodeGeneration.Rust.Tests, Aspire.Hosting.CodeGeneration.TypeScript.Tests, Aspire.Hosting.Containers.Tests, Aspire.Hosting.DevTunnels.Tests, Aspire.Hosting.Docker.Tests, Aspire.Hosting.Dotnet.Tests, Aspire.Hosting.DotnetTool.Tests, Aspire.Hosting.EntityFrameworkCore.Tests, Aspire.Hosting.Foundry.Tests, Aspire.Hosting.Garnet.Tests, Aspire.Hosting.Go.Tests, Aspire.Hosting.Java.Tests, Aspire.Hosting.JavaScript.Tests, Aspire.Hosting.Kafka.Tests, Aspire.Hosting.Keycloak.Tests, Aspire.Hosting.Kubernetes.Tests, Aspire.Hosting.Maui.Tests, Aspire.Hosting.Milvus.Tests, Aspire.Hosting.MongoDB.Tests, Aspire.Hosting.MySql.Tests, Aspire.Hosting.Nats.Tests, Aspire.Hosting.OpenAI.Tests, Aspire.Hosting.Oracle.Tests, Aspire.Hosting.Orleans.Tests, Aspire.Hosting.PostgreSQL.Tests, Aspire.Hosting.Python.Tests, Aspire.Hosting.Qdrant.Tests, Aspire.Hosting.RabbitMQ.Tests, Aspire.Hosting.Radius.Tests, Aspire.Hosting.Redis.Tests, Aspire.Hosting.RemoteHost.Tests, Aspire.Hosting.Rust.Tests, Aspire.Hosting.Seq.Tests, Aspire.Hosting.SqlServer.Tests, Aspire.Hosting.Testing.Tests, Aspire.Hosting.Tests, Aspire.Hosting.Valkey.Tests, Aspire.Hosting.Yarp.Tests, Aspire.Managed.Tests, Aspire.Playground.Tests, Aspire.Templates.Tests, Aspire.TerminalHost.Tests

Selected PR jobs (6)

cli-starter-validation, extension-e2e, extension-unit, native-dashboard-validation, polyglot, typescript-api-compat


How these were chosen — grouped by what changed

⚠️ 40 of the 56 selected test projects come from a single change — src/Aspire.Hosting/Dcp/ContainerNetworkEndpointProvisioner.cs.

🔧 src/Aspire.Hosting/Dcp/ContainerNetworkEndpointProvisioner.cs (changed source)
→ 40 via the project graph

show 40

Aspire.Hosting.Analyzers.Tests (2 hops), Aspire.Hosting.Azure.Kubernetes.Tests (2 hops), Aspire.Hosting.Azure.Kusto.Tests (2 hops), Aspire.Hosting.Azure.Provisioning.Tests (3 hops), Aspire.Hosting.Azure.Tests, Aspire.Hosting.CodeGeneration.Go.Tests, Aspire.Hosting.CodeGeneration.Java.Tests, Aspire.Hosting.CodeGeneration.Python.Tests, Aspire.Hosting.CodeGeneration.Rust.Tests, Aspire.Hosting.CodeGeneration.TypeScript.Tests, Aspire.Hosting.DevTunnels.Tests (2 hops), Aspire.Hosting.Docker.Tests (2 hops), Aspire.Hosting.DotnetTool.Tests (2 hops), Aspire.Hosting.EntityFrameworkCore.Tests (2 hops), Aspire.Hosting.Foundry.Tests (2 hops), Aspire.Hosting.Garnet.Tests (2 hops), Aspire.Hosting.Go.Tests (2 hops), Aspire.Hosting.Java.Tests (2 hops), Aspire.Hosting.Kafka.Tests (2 hops), Aspire.Hosting.Keycloak.Tests (2 hops), Aspire.Hosting.Kubernetes.Tests (2 hops), Aspire.Hosting.Maui.Tests, Aspire.Hosting.Milvus.Tests (2 hops), Aspire.Hosting.MongoDB.Tests (2 hops), Aspire.Hosting.MySql.Tests (2 hops), Aspire.Hosting.Nats.Tests (2 hops), Aspire.Hosting.Oracle.Tests (2 hops), Aspire.Hosting.Orleans.Tests (2 hops), Aspire.Hosting.PostgreSQL.Tests (2 hops), Aspire.Hosting.Python.Tests (2 hops), Aspire.Hosting.Qdrant.Tests (2 hops), Aspire.Hosting.RabbitMQ.Tests (2 hops), Aspire.Hosting.Redis.Tests (2 hops), Aspire.Hosting.RemoteHost.Tests, Aspire.Hosting.Rust.Tests (2 hops), Aspire.Hosting.Seq.Tests (2 hops), Aspire.Hosting.SqlServer.Tests (2 hops), Aspire.Hosting.Valkey.Tests (2 hops), Aspire.Hosting.Yarp.Tests (2 hops), Aspire.Playground.Tests

🔧 src/Shared/KnownConfigNames.cs (changed source)
→ 10 via the project graph: Aspire.Dashboard.Components.Tests, Aspire.Dashboard.Tests, Aspire.Hosting.Browsers.Tests, Aspire.Hosting.Containers.Tests, Aspire.Hosting.JavaScript.Tests, Aspire.Hosting.OpenAI.Tests, Aspire.Hosting.Testing.Tests, Aspire.Managed.Tests, Aspire.Templates.Tests, Aspire.TerminalHost.Tests

🧪 tests/Aspire.Hosting.Tests/Dcp/DcpCliArgsTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Tests
→ 3 via the project graph: Aspire.Hosting.Blazor.Tests, Aspire.Hosting.Dotnet.Tests, Aspire.Hosting.Radius.Tests

📦 affected project Aspire.Cli
→ 1 test: Aspire.Cli.EndToEnd.Tests

📦 affected project Aspire.Dashboard
→ 1 test: Aspire.Templates.Tests

🧪 tests/Aspire.Cli.Tests/Commands/ConfigCommandTests.cs (changed test)
→ 1 directly: Aspire.Cli.Tests

🧪 tests/Aspire.Cli.Tests/Configuration/ConfigurationServiceTests.cs (changed test)
→ 1 directly: Aspire.Cli.Tests

🧪 tests/Aspire.Cli.Tests/Projects/AppHostConfigurationProjectorTests.cs (changed test)
→ 1 directly: Aspire.Cli.Tests

🧪 tests/Aspire.Cli.Tests/Projects/DotNetAppHostProjectTests.cs (changed test)
→ 1 directly: Aspire.Cli.Tests

🧪 tests/Aspire.Cli.Tests/Projects/GuestAppHostProjectTests.cs (changed test)
→ 1 directly: Aspire.Cli.Tests

🧪 tests/Aspire.Cli.Tests/Utils/CliTestHelper.cs (changed test)
→ 1 directly: Aspire.Cli.Tests

🧪 tests/Aspire.Hosting.Tests/Dcp/DcpExecutorTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Tests

Job reasons

Job Triggered by
cli-starter-validation affected project Aspire.Cli
extension-e2e • extension/schemas/aspire-config.schema.json, src/Aspire.Cli/Configuration/AspireConfigFile.cs, src/Aspire.Cli/Program.cs, src/Aspire.Cli/Projects/AppHostConfigurationProjector.cs, src/Aspire.Cli/Projects/DotNetAppHostProject.cs, src/Aspire.Cli/Projects/GuestAppHostProject.cs, src/Aspire.Hosting/Dcp/ContainerNetworkEndpointProvisioner.cs, src/Aspire.Hosting/Dcp/DcpOptions.cs, src/Aspire.Hosting/DistributedApplicationBuilder.cs
• affected project Aspire.Cli
extension-unit extension/schemas/aspire-config.schema.json
native-dashboard-validation affected project Aspire.Dashboard
polyglot • affected project Aspire.Cli
• affected project Aspire.Hosting.Azure.Provisioning.AppService
typescript-api-compat affected project Aspire.Cli

Selection computed for commit 13d6ff0.

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

@danegsta
David Negstad (danegsta) merged commit cc59497 into main Oct 2, 2026
664 of 667 checks passed
@microsoft-github-policy-service microsoft-github-policy-service Bot added this to the 17.0 milestone Oct 2, 2026
@aspire-repo-bot

Copy link
Copy Markdown
Contributor

Pull request created: #1809

Generated by PR Documentation Check · copilot · auto · 81.6 AIC · ⌖ 10.8 AIC · ⊞ 20.3K

@aspire-repo-bot

Copy link
Copy Markdown
Contributor

📝 Documentation has been drafted in microsoft/aspire.dev#1809 targeting release/17.0.

Documents the new containerTunnel.baseImage Aspire CLI config setting (triggered signal: pr_body_has_cli_flag_mention, evidence: PR body mentions --dcp-container-tunnel-base-image). Added: a new "Configure the container tunnel base image" subsection to reference/cli/configuration.mdx (with aspire config set containerTunnel.baseImage ... example and projection to ASPIRE_CONTAINER_TUNNEL_BASE_IMAGE), a row in reference/cli/includes/config-settings-table.md, a new ContainerTunnelBaseImage subsection under "Advanced orchestration properties" in app-host/configuration.mdx covering the --dcp-container-tunnel-base-image arg and DcpPublisher:ContainerTunnelBaseImage config key, and a cross-referencing "Configure the container tunnel base image" section in fundamentals/container-networking.mdx.

Note

This draft PR needs human review before merging.

@github-actions github-actions Bot locked and limited conversation to collaborators Nov 1, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants