Run h5serv as non-root user
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- dockerfile
- Domain
- devops
Research direction
Start with the h5serv Dockerfile and reproduce the container with a mounted host file system. Check the toc file creation failure and confirm the container's user and permissions; done means the documented Dockerfile behavior no longer prevents toc creation on a mounted directory.
Written by the indexing model from the issue text.
Description
First pass at h5serv Dockerfile created a non-root user. But when mounting a host file system, this user does not have write permissions to the directory, so toc file creation fails.
Will alter the Dockerfile to run as root for now (even though it's a mild security risk).
- Dominant language
- Dockerfile
- Stars
- 17
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 HDFGroup/hdf-docker
-
Update example to the latest hdf5 version.May be free again @jreadey claimed this 1262 days ago, and no pull request is open. Openenhancement
HDFGroup/hdf-docker#3 · 1 assignee ·
All issues in HDFGroup/hdf-docker
Similar issues
-
🐛 The Rulekeeper - An index run that gives up on the lock ends SucceededPossibly taken @github-actions claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SSWConsulting/SSW.Rules#2809 · 1 comment ·
Maintainers usually reply within 1 day
-
automated-triage type/bug type/ci
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
buckai-observatory/Automated-Cloud-Removal-and-Seamless-Satellite-Image-Mosaicking-Pipeline#46 ·
Maintainers usually reply within 1 day
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
dependencies good first issue severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
TMHSDigital/GH-Arcade#27 ·