-
Notifications
You must be signed in to change notification settings - Fork 220
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
Mount only pwd
for writing
#389
Comments
I agree it would be nice if toolbox would allow not to mount the home directory, but only the "pwd" instead! Programs installed in the toolbox will store many files in $HOME (eg How about an option to use a home directory inside the container, and mount the current directory as for example |
It is kind of nice to be able to jump into |
@njam on the second though I think that would be a good solution. At least a good option, |
I've experimented with this idea in a experimental toolbox implementation (source). I added a parameter to define which folder to mount: $ toolbox-njam create foo --mount ~/Downloads The $ toolbox-njam list
NAME IMAGE MOUNT
foo registry.gitlab.com/njam/toolbox-njam/arch-toolbox:latest /home/reto/Downloads For basic use cases it works well. But I haven't extensively tested it. For example, what will/should happen if a folder outside of $HOME is mounted? |
tlbx fork has a |
@markstos what |
Duplicate of #183 |
@debarshiray hey, the #183 is closed, but what is the solution? |
I just found out that toolbox allows to modify files outside of directory where I invoked it. I expected it to maybe allow modification outside of
pwd
but at least discard them. Now I see that it doesn't protect my files outside ofpwd
from modifications.Maybe there are some options that I missed?
UPDATE: This hack from #348 (comment) seems to work ok for now.
It does create new files in project dir, but doesn't touch parents, which is good.
The text was updated successfully, but these errors were encountered: