You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the HealthChecksUI sample in the dotnet/aspire-samples repo and Podman, the HealthChecks UI dashboard was not able to reach the healthchecks URIS:
with looking at the logs exceptions:
GetHealthReport threw an exception when trying to get report from http://host.containers.internal:61669/healthz configured with name webfrontend.
System.Net.Http.HttpRequestException: Connection refused (host.containers.internal:61669)
---> System.Net.Sockets.SocketException (111): Connection refused
This operates differently when just using Docker and the host.docker.internal URIs don't seem to be impacted, but Podman and the mappings used in the Podman machine network config seem to impact these situations where a container needing to accessing something at the host.containers.internal URI may fail given this issue.
The text was updated successfully, but these errors were encountered:
Using the HealthChecksUI sample in the dotnet/aspire-samples repo and Podman, the HealthChecks UI dashboard was not able to reach the healthchecks URIS:
with looking at the logs exceptions:
This appears to be a common issue with Podman 5+ presently: containers/podman#22237
This operates differently when just using Docker and the host.docker.internal URIs don't seem to be impacted, but Podman and the mappings used in the Podman machine network config seem to impact these situations where a container needing to accessing something at the host.containers.internal URI may fail given this issue.
The text was updated successfully, but these errors were encountered: