-
Notifications
You must be signed in to change notification settings - Fork 98
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
RFE: --copy-up remap #256
Comments
This may be more involved than simply allowing for a remapping, given the functionality of For instance, I'm genuinely torn between the functionality of |
It just occurred to me that I should be able to achieve this with a bind mount. However, adding this as a built-in capability would be particularly useful for a streamlined process. Maybe something like |
SGTM |
It might be useful to expand the
--copy-up
argument to accept syntax for remapping the source to a different destination.For instance, my particular use-case involves chrooting on entry, but simply due to the nature of chrooting, critical directories (like
/run/
,/etc/
, and others) are not available in the chrooted filesystem.For additional context, my overall goal of this is to create an isolated system that can be modified without affecting the host filesystem. Specifically, I have a directory structure that mimics a Linux installation, including things like
/home
. I'd like changes to the user dir to be isolated to this particular directory structure, rather than having file changes/additions/deletions affecting the actual/home
dir on the host system. Currently, I'm not fully aware of a way to accomplish this without creating hard-links to the directories that I want to "copy-up". I'm about to test this method, but it's also not entirely ideal.Feature Request
Argument
--copy-up
could accept a syntax like:rootlesskit --copy-up=/etc:./etc
. Or, a new argument that would accept this type of logic, like--map-up
or something.The text was updated successfully, but these errors were encountered: