Add NerdCTL
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the repository's Dockerfile and reviewing how the Kubernetes investigation image is built. Determine how NerdCTL should be included, then verify the built image contains the requested tool and preserves the existing debugging setup.
Written by the indexing model from the issue text.
Description
Useful tool
- Dominant language
- Dockerfile
- Stars
- 169
- Forks
- 36
- Avg merge
- 6d 20h
- Merged PRs (30d)
- 1
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.
More from digitalocean/doks-debug
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
digitalocean/doks-debug#22 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
digitalocean/doks-debug#9 · 1 comment ·
All issues in digitalocean/doks-debug
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
danielmiessler/LifeOS#2215 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100