ObolNetwork / ObolNetwork/obol-stack
Check for resources
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Check the resources allocated via docker desktop so users don't find themselves with k3d crashing
Ressources:
- docker info
- charon test
Contributor guide
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 running docker info and charon test to understand the available resource information and current checks. Trace how k3d is started, then define and verify the resource validation needed to prevent k3d from crashing when Docker Desktop has insufficient allocation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100