-
Notifications
You must be signed in to change notification settings - Fork 76
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
[macOS] Mounted directory is not accessible in the chroot environment #95
Comments
So summary, /tmp/new_root/usr/bin can be listed outside of the chroot, but not from the inside? Also, is 'ls' itself failing or does 'readdir' or 'stat' fail? I.e. could you please provide 'strace' output (I have that macOS has strace...) for your 'ls /usr/bin' command? |
Yes - summary is correct. strace ? did you mean, stderr output of this tool ? (with
|
I mean output of 'strace -f ls /usr/bin'. Or if 'cat' also failing, 'strace -f cat /usr/bin/{some_failing_file}'. Debug output from 'unionfs -d -o debug_file=<some_log_file>' would also help, |
Actually strace is linux specific. I found that macOS have dtrace. Which was also not working out for me, I tried do what they suggested ( |
for anyone landing here, i managed to workaround the issue by doing a bindfs mount on the unionfs mount originally you would do:
with the workaround:
then when you unmount, you unmount the bindfs first
|
Steps to reproduce this issue in macOS.
/tmp/new_root
The text was updated successfully, but these errors were encountered: