Closed NAVRockClimber closed 1 year ago
So, you are saying that the container works - but it registers as unhealthy? If you use -doNotCheckHealth - does it then work?
Hi Freddy, yes it seems to be just the healthcheck that fails. At least I can reach the webclient now if I disable the healthcheck like you proposed. I did not test more, yet.
Unfortunately the healthcheck is also critical for a tooling like ours at Cosmo.
If I manually invoke the health endpoint in the container I get an error message:
Invoke-WebRequest -Uri "http://Test/BC/Health/System" -UseBasicParsing
Invoke-WebRequest : {"result":false}
At line:1 char:1
+ Invoke-WebRequest -Uri "http://Test/BC/Health/System" -UseBasicParsin ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
Looks like a bug in next major. Will file a bug on the client team
They accepted the bug, should be fixed within a few days.
Thanks, Freddy.
PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue If I create a nextmajor container it does not become healthy which is critical if you are e.g. in docker swarm or kubernetes environment behind a reverse proxy. I checked the event log and found the error below.
Testing: #2907
Scripts used to create container and cause the issue
Full output of scripts
New-BCImage:
New-BcContainer:
Screenshots If applicable, add screenshots to help explain your problem.
Additional context