-
Notifications
You must be signed in to change notification settings - Fork 4
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
do we really need the bind functionality? #9
Comments
There are two types of bind mount done by the linux-user-chroot backend. 1 is using linux-user-chroot's The 2nd type is I don't know the exact details of the problem you're seeing, but it may be due to the really stupid amount of To fix this, I can only think of one option: add a |
On Thu, Jul 02, 2015 at 01:49:03AM -0700, Sam Thursfield wrote:
For reference, the huge list of --mount-readonly binds was the last resort. It should be possible to make the root bind read-only and explicitly mark Bind-mount behaviour was in this grey area when I did this investigation.
If the problem is that there's too many binds for the old version's arbitrary |
i've noticed that if the directory structure changes (eg another program deletes a directory while sandboxlib is running), we can hit 'mount (MS_BIND): No such file or directory'
The text was updated successfully, but these errors were encountered: