Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request: really simple UNPRIVILEGED support #26

Open
schmonz opened this issue Aug 12, 2018 · 2 comments
Open

request: really simple UNPRIVILEGED support #26

schmonz opened this issue Aug 12, 2018 · 2 comments

Comments

@schmonz
Copy link

schmonz commented Aug 12, 2018

I'd find it very useful if pkg_comp, still using sandboxctl and requiring root to run, could be configured to create an unprivileged user inside the sandbox and do an --unprivileged build as that user.

I'd use this in a VM configured to match the OS of a hosting provider where I have shell access but can't compile much of anything (thanks to process limits). I'd build binary packages in the VM, taking care that the sandbox $HOME matches my hosting provider $HOME, and then upload and install them.

@jmmv
Copy link
Owner

jmmv commented Sep 4, 2018

Haven't thought much about this, but what settings would you need for this to work properly in your environment? I can imagine having to tell pkg_comp at least these:

  • User details: name, UID, primary GID, maybe supplementary GIDs, home directory.
  • Group details: name, GID (optional; just in case the user has to belong to a special group).
  • Whether to use --unprivileged or not.

Anything else?

@schmonz
Copy link
Author

schmonz commented Sep 12, 2018

That sounds right in general. For my particular case, I suspect I could get by with as little as username, home dir, and --unprivileged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants