Skip to content

[release/9.4] Throw if container runtime is unhealthy during image build - #10400

Merged
Karol Zadora-Przylecki (karolz-ms) merged 1 commit into
release/9.4from
backport/pr-10399-to-release/9.4
Jul 15, 2025
Merged

Karol Zadora-Przylecki (karolz-ms) merged 1 commit into
release/9.4from
backport/pr-10399-to-release/9.4

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 14, 2025 •

Copy link
Copy Markdown
Contributor

Backport of #10399 to release/9.4

/cc Safia Abdalla (@captainsafia)

Customer Impact

  • The fix adds a health check at the start of ResourceContainerImageBuilder.BuildImagesAsync. If the runtime isn’t running, we now log an error and throw InvalidOperationException with a clear message, immediately failing the publish step

Testing

  • Unit tests added in ResourceContainerImageBuilderTests
  • Manual validation: stopped Docker daemon and confirmed the new exception and log entry appear and that publish

Risk

Low. The change is isolated to the image-building path and is only triggered when the container runtime is unhealthy.

Regression?

No.

@captainsafia

Copy link
Copy Markdown
Contributor

@dotnet/aspire-push Can I get help merging this?

@karolz-ms
Karol Zadora-Przylecki (karolz-ms) deleted the backport/pr-10399-to-release/9.4 branch July 15, 2025 17:38
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants