Skip to content

fix(lab): clear orphaned Aspire tunnel-proxy containers on every stop - #263

Merged
hoangsnowy merged 1 commit into
mainfrom
fix/lab-orphan-proxies
Oct 22, 2026
Merged

hoangsnowy merged 1 commit into
mainfrom
fix/lab-orphan-proxies

Conversation

@hoangsnowy

Copy link
Copy Markdown
Owner

Summary

The lab update after #262 never became healthy: the new AppHost started its dashboard but created no Postgres/Keycloak containers. 77 orphaned aspire-container-network-tunnelproxy-* containers had piled up (a hard-killed AppHost never removes them; lab updates + AppHosts started by test/preview runs). After removing them the lab came up at once.

Stop-Lab now calls Remove-OrphanTunnelProxies: removes only those proxy containers whose creating process (labels: pid + start time) no longer exists.

Test plan

  • Ran the function on this box: kept the live lab's proxy, removed none of anything else.
  • Manual cleanup of the 77 orphans → lab.ps1 down/up healthy, runner paired.

🤖 Generated with Claude Code

https://claude.ai/code/session_018WAdQ7Rm24xss5QDSvXtJB

A hard-killed AppHost never removes its network tunnel-proxy containers; 77 had piled up (lab updates plus every
AppHost a test or preview run started) and a fresh lab AppHost created no containers at all — the update never became
healthy. Stop-Lab now removes the aspire-container-network-tunnelproxy-* containers whose creating process (recorded
in their labels, pid + start time) is gone. Nothing else is touched.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018WAdQ7Rm24xss5QDSvXtJB
@hoangsnowy
hoangsnowy merged commit a60f094 into main Oct 22, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant