aspire-container-health-checks

Configure HTTP health checks for .NET Aspire container services.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill aspire-container-health-checks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-container-health-checks
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.claude/skills/aspire-container-health-checks
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill aspire-container-health-checks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves race conditions where containers report as running before their internal services (like database migrations or realm imports) are actually ready to accept traffic.

Core Features & Use Cases

  • Initialization Validation: Configures health checks to probe application-specific endpoints rather than generic process states.
  • Circular Dependency Prevention: Provides patterns to avoid deadlocks between proxy resources and their upstream containers.
  • Use Case: When deploying Keycloak via Aspire, use this skill to ensure the container waits for the realm import to complete before downstream services attempt to connect.

Quick Start

Use the aspire-container-health-checks skill to configure a custom HTTP health check for a container resource in your AppHost Program.cs file.

Frequently Asked Questions about aspire-container-health-checks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my .NET Aspire container report as running before it is ready to accept traffic?

Aspire container health checks resolve race conditions where generic process states report running before internal initialization workflows complete. Configuring precise HTTP health checks probes application-specific endpoints to verify actual service readiness.

How do I configure HTTP health checks for containerized services in .NET Aspire?

To configure HTTP health checks in .NET Aspire, apply this skill to your AppHost Program.cs file. It sets up custom HTTP probes that validate application-specific endpoints rather than relying on basic container process states.

How do I prevent circular dependency deadlocks between proxy resources and upstream containers in Aspire?

Preventing circular dependency deadlocks in Aspire involves applying specific health check patterns that ensure upstream containers fully finish initialization before downstream proxy resources attempt to establish connections.

Does this approach work for complex multi-container environments with database migrations?

Yes, this approach suits complex multi-container environments by validating application-specific endpoints. It ensures containers wait for internal workflows like database migrations or realm imports to complete before routing traffic.

What is the best way to ensure Keycloak container readiness in Aspire before downstream services connect?

The best way to ensure Keycloak readiness in Aspire is configuring custom HTTP health checks. This guarantees the container waits for realm imports to finish, preventing premature connection attempts by downstream services.