Skip to content

sysbox-fs/seccomp: add CIFS/SMB3 mount proxy#118

Open
VitorRamos wants to merge 1 commit intonestybox:masterfrom
VitorRamos:cifs
Open

sysbox-fs/seccomp: add CIFS/SMB3 mount proxy#118
VitorRamos wants to merge 1 commit intonestybox:masterfrom
VitorRamos:cifs

Conversation

@VitorRamos
Copy link
Copy Markdown

Extend processNfsMount to also handle "cifs" and "smb3" filesystem types. The existing NFS proxy already does exactly what CIFS needs: re-issue mount(2) via nsenter as host root (AllNSsButUser).

  • mount.go: add "cifs", "smb3" to the processNfsMount dispatch case; update function comment; use m.FsType in the debug log

Tested: ubuntu:24.04, cifs-utils 7.0, guest share, vers=3.1.1

Fixes #856

@VitorRamos
Copy link
Copy Markdown
Author

VitorRamos commented Apr 6, 2026

Hi,

We’ve been running into some SMB/CIFS mount limitations when using Sysbox. We’re currently testing it in our Coder setup (https://coder.com/docs/admin/templates/extending-templates/docker-in-workspaces), and so far this has been the main blocker.

Would this kind of change be something you’d consider accepting?

Thanks!

Extend processNfsMount to also handle "cifs" and "smb3" filesystem types. The existing NFS proxy already does exactly what CIFS needs: re-issue mount(2) via nsenter as host root (AllNSsButUser), satisfying the kernel's requirement for CAP_SYS_ADMIN in the initial user namespace.

- mount.go: add "cifs", "smb3" to the processNfsMount dispatch case; update function comment; use m.FsType in the debug log

Tested: ubuntu:24.04, cifs-utils 7.0, guest share, vers=3.1.1

Fixes [#856](nestybox/sysbox#856)

Signed-off-by: vramosgo <ramos.vitor89@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Permission Denied: mount of cifs inside sysbox container not working

1 participant