Health check UI is not working (Apple M1 with Docker)
See original GitHub issueI am starting the solution with docker-compose up
.
The shop UI works, as well as the services/APIs.
However, when trying to navigate to the health check UI at http://localhost:5107/healthchecks-ui
, I get this:
Did anyone ever see this? Where to best look for errors?
Thanks.
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Docker Desktop cannot start on mac M1 chip · Issue #6145
I tried to re-install it and it doesn't work for me. The troubleshoot function is still not working and any operation has no...
Read more >Blank window issue with many third-party apps
Blank window issue with many third-party apps. I'm using a MacBook Air M1 (2020), OS: Monterey 12.4 but I encountered the same issues...
Read more >Why is docker killing my mbp
I have a new MBP 16 (intel) with 16gb of ram, 1tb and a dedi gpu. It's always been kind of slow but...
Read more >Docker healthcheck for nginx container
It looks like the problem is just an issue with systemd never returning from the status check when the container initially launches, and...
Read more >Docker Desktop release notes
For Mac. Added a health check for macOS that notifies users if there has been a change on their system which might cause...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @ChristianWeyer,
Yes, I’m planning to find a fix for this (my main desktop is a M1 Mac Mini, so I’d really like eShopOnDapr to run smoothly on it 😉 ). However, I’m unable to give an exact date for a fix as I don’t have much time at the moment to spend on this project. It’ll probably be second half of May.
It’s interesting that it’s only the
xabarilcoding/healthchecksui
container that has the issue. The other containers also use .NET app settings with the JSON file configuration provider and don’t have the issue. Perhaps a difference in .NET version? My first try for a fix would be to create a newWebStatus
microservice that uses the AspNetCore.Diagnostics.HealthChecks package to incorporate the health dashboard instead of directly using their container image (in fact, this is actually the way it was in the original solution). PR’s very welcome 😊BTW: I changed SQL Server to this version, for it to work on M1:
mcr.microsoft.com/azure-sql-edge