max-mapper / max-mapper/HyperOS
run chroot as non-root
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 124
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
some chroot implementations have a --userspec arg to specify the user the chroot should run as. but it doesn't look like the busybox chroot does:
chroot: can't execute '--userspec=admin:admin': No such file or directory
perhaps we can create an admin user, give it chroot privs, then run chroot as that user. or maybe we can chroot as root then immediately drop privileges somehow
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 by locating the BusyBox chroot invocation and the distribution's user setup. Check the available BusyBox chroot options and the existing privilege model before choosing an approach. Done means the chroot workload runs as a non-root user without breaking the container startup path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100