stacks-network / stacks-network/hacknet
Stop Prometheus and cAdvisor in `down-xyz` targets
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Right now, the down-xyz Makefile targets don’t stop the Prometheus and cAdvisor containers. If you forget to stop them manually, they can pollute future runs with leftover data. These containers should be stopped automatically when running any down-xyz target.
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 inspecting the Makefile's down-xyz targets and how the Prometheus and cAdvisor containers are managed. Run each down-xyz target and verify that both containers stop automatically and no longer leave data affecting later runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100