mismatching subuid and subgids range
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
After installing from source on latest master (7e221e0f540793277caeeee4b09b14ad4c0970b2), I was hitting the following error:
failed to create sysbox-mgr: failed to setup subid allocator: could not find matching subuid and subgids range for user sysbox.
It seems that sysbox-mgr generated two different ranges in /etc/subuid and /etc/subgid - if I understand the code here correctly, the ranges should be identical to be accepted.
So, I think there are a few issues here;
sysbox-mgrshould not generate mismatching ranges.- I could not find this requirement in the documentation or troubleshooting guide.
- The error message also feels a bit misleading: I interpreted it as that no subuid and subgids ranges were fond matching the user sysbox.
With some directions, I'd be happy to help resolve this!
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 subidAlloc/subidAllocSimple.go at the linked range-allocation code and reproduce the mismatch between /etc/subuid and /etc/subgid. Check the documentation and troubleshooting guide for the missing requirement, then review the reported error wording. Done means the ranges agree and the behavior and message are documented or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- devops, operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100