I've been using Aspire successfully with Podman for months, but I've just updated to Podman desktop 1.29/Podman 6.0.2 and suddenly all of my containers (cosmosdb preview, redis, eventhub emulator) are getting stuck in the Running but Unhealthy.
If I look at the logs of the containers, they all appear to be good to go, for example in the eventhub container I can see the log "Emulator Service is Successfully Up!" but Aspire isn't detecting this for some reason.
In the cosmosdb log I can see the following log:
=== LEGACY COMPATIBILITY MESSAGE ===
Below is a legacy message which can be removed any time - please use the health probe instead
System is now fully ready to accept requests
Now listening on: https://0.0.0.0:8081
====================================
That IP is suspicious, and the data explorer fails to connect.
I've rebooted and wiped all images/containers/volumes from podman to remove any stale data.
I've been using Aspire successfully with Podman for months, but I've just updated to Podman desktop 1.29/Podman 6.0.2 and suddenly all of my containers (cosmosdb preview, redis, eventhub emulator) are getting stuck in the Running but Unhealthy.
If I look at the logs of the containers, they all appear to be good to go, for example in the eventhub container I can see the log "Emulator Service is Successfully Up!" but Aspire isn't detecting this for some reason.
In the cosmosdb log I can see the following log:
That IP is suspicious, and the data explorer fails to connect.
I've rebooted and wiped all images/containers/volumes from podman to remove any stale data.