[imposm] Container should not run as root
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Begin with the imposm container configuration; the issue provides no file or test path, so trace where that image's user is set. Done means the container starts and runs as a non-root user, with the repository's existing validation used if available.
Written by the indexing model from the issue text.
Description
#13
- Dominant language
- Dockerfile
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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 MapColonies/microcOSM
-
Difficulty 3/5 1-2 days Newbie friendliness 40/100
MapColonies/microcOSM#140 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 20/100
MapColonies/microcOSM#84 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 15/100
MapColonies/microcOSM#82 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
MapColonies/microcOSM#81 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
MapColonies/microcOSM#80 ·
All issues in MapColonies/microcOSM
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug build
Difficulty 1/5 Under an hour Newbie friendliness 91/100
facebookincubator/velox#19194 ·