Best practices for sudo inside enroot container

Open
#262 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
shell
Domain
operating-systems

Research direction

Start by reviewing enroot.conf and the available SPANK options, then compare their behavior with the reported ssh localhost workaround for running sudo dmesg outside the container. Done would be a documented, supported way to handle host sudo escalation from an enroot container, or a clear statement that no such configuration exists.

Written by the indexing model from the issue text.

Description

Hi Enroot Team! Thanks for this wonderful tool. I know enroot is designed to be lightweight and avoids complexity but I am wondering about best practices around sudo based escalation inside enroot containers. Based on my research I have yet to find a way to allow a user inside an enroot container to run something like sudo dmesg. Is there a best-practice way to allow this. In most cases my users are members of the sudoers group on the host machine. On trick I have found is to use ssh localhost <command> to run the command outside the enroot and on the host. Is there a setting in enroot.conf or a combination of the spank options I can use to do this without the ssh "hack"?

Thanks, Stephen.

Dominant language
Shell
Stars
1.1k
Forks
139
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/enroot

All issues in NVIDIA/enroot

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.