nestybox / nestybox/sysbox-runc
Add a configuration flag option to increase the 65536 subordinate range limit
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 37
- Forks
- 43
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 1
Description
Need for enhancement:
For legacy reasons, we have to maintain compatibility for a user with large UID, much higher than the 65536 limit [0] which sysbox uses for its allocations. This means that any attempts to chown resources for this user will break. We have experimented with using Docker's userns-remap setting to extend this range, but then we cannot take advantage of sysbox's dynamic allocation.
Description of enhancement:
The default IdRangeMin would not change. We would follow the best practices for introducing a configuration option that lets us run with an increased range. We would validate that 268435456 divides the setting evenly so that sysbox's overall range can be subdivided evenly.
https://nestybox-support.slack.com/archives/CS7V68QMP/p1740792462742969
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 at libsysbox/syscont/spec.go near the referenced 65536 limit and trace how IdRangeMin is used and configured. Add the requested configuration option while preserving the default, validate that 268435456 divides the configured range evenly, and verify the allocation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100