Support read-only root fs and non-root user
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 178
- Avg merge
- 15d 9h
- Merged PRs (30d)
- 2
Description
Output of rest-server --version
restic/rest-server:0.12.1
What should rest-server do differently?
Run the rest-server binary as a non-root user and add integration tests that verify this image can be run with a read-only root file system.
What are you trying to do? What is your use case?
Modern container security policies require that containers run as non-root users and that the image is mounted read-only. One of the tools that verifies this is kubelint (for k8s). This tool is currently the one that complains in my environment.
Did rest-server help you today? Did it make you happy in any way?
rest-server reliably offers backups for me in conjunction with k8up. I was repeatedly able to restore files that my main server lost due to various reasons. Thanks to the use of HTTP as a transport protocol, the transport between sites is extremely easy to get through the firewall for me. Please keep up the good work!
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 with the rest-server binary and the container image configuration, then identify how the integration tests are run. Done means the image runs as a non-root user with a read-only root filesystem and integration tests verify both requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- devops, security, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100