Icinga / Icinga/docker-icinga2
Make use of Dockerfile HEALTHCHECK feature
Open
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 73
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
so that Compose can tell whether we actually started successfully.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's Dockerfile and the Docker Compose health-check behavior described in the issue. Define the container health condition from the existing image behavior, then verify that Compose can distinguish a successfully started container from a failed one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, dockerfile
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100