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
I think the problem might be caused by the OTLE endpoint being served on a self-signed certificate from the Aspire app host, which then isn't trusted in the container. This is mostly a problem with container resources because executable resources run on the host which the aspnet dev cert is trusted, whereas inside the container it hasn't been trusted.
The way the networking is configured with Docker the endpoint that it access it via, host.docker.internal:<some port>, is available within the container, but the SSL certificate for the OTEL endpoint isn't valid so it fails.
We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use /stale-extend to extend the window.
We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use /stale-extend to extend the window.
We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use /stale-extend to extend the window.
Just tested this with the new Aspire 13 support for automatically trusting the dev cert and telemetry is flowing automatically, even over https when WithOtlpSupport() is added to a go feature flags resource.
Activity
aaronpowell commentedon Feb 6, 2025
I think the problem might be caused by the OTLE endpoint being served on a self-signed certificate from the Aspire app host, which then isn't trusted in the container. This is mostly a problem with container resources because executable resources run on the host which the aspnet dev cert is trusted, whereas inside the container it hasn't been trusted.
Odonno commentedon Feb 6, 2025
I trust you on that. I am also unsure if it is related to the private IP address, can't the OTEL endpoint be consumed via its service name?
aaronpowell commentedon Feb 7, 2025
The way the networking is configured with Docker the endpoint that it access it via,
host.docker.internal:<some port>, is available within the container, but the SSL certificate for the OTEL endpoint isn't valid so it fails.github-actions commentedon Feb 28, 2025
We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use
/stale-extendto extend the window.Odonno commentedon Feb 28, 2025
/stale-extend ?
github-actions commentedon Mar 22, 2025
We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use
/stale-extendto extend the window.github-actions commentedon Apr 6, 2025
This issue has been stale for 5 weeks and has been automatically closed.
github-actions commentedon Oct 13, 2025
We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use
/stale-extendto extend the window.github-actions commentedon Oct 27, 2025
This issue has been stale for 5 weeks and has been automatically closed.
danegsta commentedon Nov 12, 2025
Just tested this with the new Aspire 13 support for automatically trusting the dev cert and telemetry is flowing automatically, even over https when
WithOtlpSupport()is added to a go feature flags resource.danegsta commentedon Nov 12, 2025
@aaronpowell this should only require adding
WithOtlpSupport()to the defaults forAddGoFeatureFlag.Odonno commentedon Feb 2, 2026
I still have the issue unfortunately. But now I strongly believe this might be due to Podman in some way.