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
If you only set it to be "/healthcheck" the underlying cloudformation script will set it to use CMD-Shell. The ADOT collector does not come with a default shell.
Describe the bug
As per the documentation and the examples in this repository, we can set the ECS
healthCheck
to the "/healthcheck" command.After deploying the ADOT collector with this, the container remains unhealthy in ECS
Steps to reproduce
Deploy the ADOT collector with a
healthcheck
command as described in the documentationWhat did you expect to see?
The container is becomes healthy after a few seconds
What did you see instead?
The container stays unhealthy forever
Environment
I'm using AWS CDK. Here's my container definition:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: