microsoft / microsoft/aspire.dev

[GitHub Discussions] Docker & Container documentation gaps

Open
#359 0 comments 0 reactions 1 assignee View on GitHub

@danegsta is already working on this.

Since Feb 9, 2026.

external feedback
Dominant language
MDX
Stars
193
Forks
87
Avg merge
1d 22h
Merged PRs (30d)
73

Description

Summary

Based on analysis of 820 GitHub discussions from dotnet/aspire.

Question counts:

Topic Questions
Docker/Containers 156 total
Container Build 40+
Volumes/Persistence 25+
Docker Compose 20+
Registry 15+
Networking 20+

Gaps in Existing Docs

1. ✅ Docker Compose Publishing - WELL DOCUMENTED

Docs exist: docker-integration ✅ comprehensive coverage

The doc covers:

  • AddDockerComposeEnvironment and PublishAsDockerComposeService
  • aspire publish, aspire do prepare-{name}, aspire deploy
  • Environment file customization
  • Container registry configuration (AddContainerRegistry)
  • GitHub Actions workflow example
  • Image push with aspire do push

Remaining questions:

What might be missing:

  • Cross-platform build consistency troubleshooting
  • Platform architecture configuration details

2. ⚠️ Container Build Troubleshooting

Docs exist: docker-integration, add-dockerfiles-to-your-app-model ✅

Discussions:

What's missing:

  • Cross-platform container build troubleshooting
  • Container inclusion/exclusion configuration
  • Rebuild behavior control (avoiding unwanted rebuilds)

3. ✅ Volume/Persistence - WELL DOCUMENTED

Docs exist: persist-aspire-project-data-using-volumes-or-bind-mounts, persistent-container-lifetimes ✅

Remaining questions:

What might be missing:

  • Volume naming conflict resolution
  • Database backup/restore with volumes

4. ✅ Container Networking - WELL DOCUMENTED

Docs exist: inner-loop-networking-overview ✅ comprehensive

The doc covers:

  • Container bridge networks (aspire-session-network, aspire-persistent-network)
  • DNS-based service discovery between containers
  • host.docker.internal behavior
  • Container-to-container communication

Remaining questions:

What might be missing:

  • Container-to-localhost SQL Server specific patterns
  • External network exposure (0.0.0.0 binding)

5. ⚠️ Alternative Runtimes

Docs exist: None for Podman or alternative runtimes

Discussions:

What's needed:

  • Podman support documentation
  • Running without Docker scenarios
  • Alternative container runtime support status

Data Source

  • GitHub Discussions: 820 total
  • Docker/Container-related: 156 discussions
  • Date range: Project inception - February 2026
  • Verified against: aspire-list_docs (12 container/docker docs), aspire-get_doc for detailed review

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.