aws / aws/containers-roadmap

[ECS] [request]: Take Docker image HEALTHCHECK into account when available

Open
#1,041 7 comments 45 reactions 0 assignees View on GitHub
ECS Fargate Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Use the `HEALTHCHECK` defined in the Docker image instead of forcing us to repeat ourself and add the same information to the task definition once again.

**Which service(s) is this request for?**
Fargate, ECS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
In my Dockerfile, I have configured a `HEALTHCHECK`. Unfortunately, ECS doesn't pick up this information. I see that the healtchecks are performed in the container logs but ECS does not seem to fetch this information. It would be so much easier if ECS would just use the information that is already available.

**Are you currently working around this issue?**
I just don't use healthchecks. Configuring them in CloudFormation for 3 containers with parameters is just crazy (15 parameters needed out of 60 available...).

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the Dockerfile HEALTHCHECK behavior and the ECS/Fargate task definition health-check settings described in the request. Done means ECS can use the image's available health-check information without requiring the same parameters to be repeated for each container.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, docker
Domain
cloud, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.