You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have permission issues with mounting SMB share using mount -t cifs and without sysbox its working well with right capabilities, but with sysbox it throws permission error, probably sysbox while intercepting the mount calls denying the mount of cifs?
With Sysbox:
without uid gid also same error, Without Sysbox its working well.
I did some research and read other threads and found @ctalledo recommending this
In the meantime, a work-around in order to mount a cifs-backed volume into a Sysbox container would be to configure Docker in userns-remap mode. This way Sysbox won't need to use shiftfs anymore.
If you want to do this, add the "userns-remap" line to the /etc/docker/daemon.json file
but I cant use this since my infra relies on network_mode: host, and with userns-remap, host network is not possible since it affects even the runc containers.
Is there a workaround for this today?
My requirement comes from having a file system that needs mandatory file locking, and I ended up using SAMBA.
The text was updated successfully, but these errors were encountered:
The permission denied problem is likely coming from CIFS itself (maybe due to the username, password, or uid/gid options) or possible permissions on the Samba share itself. I was not able to reproduce on my local Linux environment.
I have permission issues with mounting SMB share using
mount -t cifs
and without sysbox its working well with right capabilities, but with sysbox it throws permission error, probably sysbox while intercepting the mount calls denying the mount of cifs?With Sysbox:
I did some research and read other threads and found @ctalledo recommending this
but I cant use this since my infra relies on network_mode: host, and with userns-remap, host network is not possible since it affects even the runc containers.
Is there a workaround for this today?
My requirement comes from having a file system that needs mandatory file locking, and I ended up using SAMBA.
The text was updated successfully, but these errors were encountered: