-
Notifications
You must be signed in to change notification settings - Fork 160
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
umount2 fails with ENOENT (No such file or directory) #854
Comments
Hi @gabrielrussoc, thanks for trying Sysbox and reporting the issue. Can you provide the output of |
@ctalledo here you go
|
also just for clarity, I published the image from the repro on docker hub: So you can peak what the script does and hopefully even repro yourself if that helps you (appreciate the security concern of running an admin container, but I'm using some cheap AWS VMs to repro this) Here's the docker file:
And here's the python script sample_fuse.py:
|
@ctalledo does the above give any clues of what could be wrong? any bells ringing ? |
repro
Step 1: mount and work with FUSE inside sysbox containers:
Inside the container, I have a sample python script to create a simple passthrough FUSE:
Step 2:
Try unmount the filesystem and see it failing with No such file or directory:
sanity check
The exact same steps DO NOT repro if running with
--runtime=runc
like:it's possible to umount2 just fine on the default runc
some initial investigation
If we run fusermount with
strace
, we can see the syscall failing isumount2
:It seems like
umount2
is always intercepted by sysbox per this comment:https://github.com/nestybox/sysbox-runc/blob/1b440ff266841f3d2d296e664122a9e29ceb9fd8/libsysbox/syscont/syscalls.go#L371-L384
And indeed we do some file access checks:
https://github.com/nestybox/sysbox-fs/blob/da7644ded8f9430b9cc5c4afc50d9edd115da0f7/seccomp/tracer.go#L713-L718
unclear what to do from here -- I'm really not familiar with any of these
version
The text was updated successfully, but these errors were encountered: