Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Podman-hosted containers may not be able to reach Aspire services #4136

Open
timheuer opened this issue May 9, 2024 · 0 comments
Open

Podman-hosted containers may not be able to reach Aspire services #4136

timheuer opened this issue May 9, 2024 · 0 comments
Labels
area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication area-orchestrator

Comments

@timheuer
Copy link
Member

timheuer commented May 9, 2024

Using the HealthChecksUI sample in the dotnet/aspire-samples repo and Podman, the HealthChecks UI dashboard was not able to reach the healthchecks URIS:

Image

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 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.

@DamianEdwards DamianEdwards added area-orchestrator area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication and removed area-dashboard labels May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication area-orchestrator
Projects
None yet
Development

No branches or pull requests

2 participants