You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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).
I'd find it very useful if
pkg_comp
, still usingsandboxctl
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.The text was updated successfully, but these errors were encountered: