Please support dynamic user namespaces
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
docker-entrypoint.sh currently makes it very hard to run a Nextcloud container in an isolated dynamic user namespace. Because UIDs are not known on the host before starting a container in such an environment, setting the correct file permissions to allow fine grained write access for the user running fpm or apache is impossible.
Looking at some other entrypoints usually this problem is mitigated by a simple chown -R.
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 with docker-entrypoint.sh and inspect how it currently sets ownership and permissions before fpm or Apache runs. Compare the linked MariaDB, PostgreSQL, and Synapse entrypoints for their recursive chown handling. Done means the Nextcloud container can run with a dynamic user namespace while preserving the required write access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100