Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Proposal: Allow execute on shared folders (mount w/out noexec) #290
I did not know I had an issue with executing on a docker container using a shared folder. The reason I believed I could execute is because when changing the ACL for a share the options are read/write/execute. Interesting enough when you add a share the GUI only shows read/write. If you change the privileges you don't see execute. To further the confusion after adding a share and looking the ACL, execute is set and it is an option in the drop downs.
Part of this is due to my (mis)understanding of execute bit at the file/folder level and what execute or noexec means on the mount point.
Some of these suggestion might be off, but I think the point I'm getting at can be understood. Again I don't understand the overlap between noexec and the execute bit and why you have noexec and yet the bit turned on. @ryecoaaron explained a little bit, I will do more research.
Here are some suggestions
I know with data you don't need to execute, but I think by expanding OMV to have docker, the growth and acceptance of docker the doors are opening to more possibilities for OMV beyond just data. When I first set out on my NAS journey I thought all I was going to have was storage. Now I have a development server, awesome! I can bring the cloud into my development shop! Next it will be multiple OMVs and Kubernetes!
Before I could do anything though I had to spend two hours figuring out why I see execute turned on in the ACL, but I can't execute.