Posts by y2k4life

@ryecoaaron I agree, now that I see that disabling it caused the issue. Because it can be disable maybe, like me, this is the cause of the problems for other people. I was being a minimalist and only enabling the options I needed, which was docker. I did not know, nor was it clear, that OMV-Extras.org is a base repo that the other repos are dependent on, that by disabling it would cause problems. I just assumed OMV-Extras.org was repo with some of the plug-ins.

What I had to do was to enable OMV-Extras.org repo.

1. Expand System
2. Select OMV-Extras
3. Make sure OMV-Extras.org is enabled

"Depends: openmediavault-omvextrasorg (>= 4.1.15) but 4.1.13 is to be installed"

I was getting the same errors, followed @ottoking was doing and thought that it might be because the repository can't be reached.
Sure enough OMV-Extras.org was disabled

Filed an issue Proposal: Allow execute on shared folders (mount w/out noexec)
I understand the security concern, that is why I suggest having a disclaimer, if you don't know what you are doing don't change. Yes the change is simple but outside the box and having to poke around config files and reading the threads it seems to be conflicting place to do it. Environment variable, XML, run a command to put in fstab, etc. But if you know enough to be dangerous it can be done as in my case.

I don't know what is more of a danger, someone poking around and making changes to files that if they do it wrong breaks the server or having an easy way of doing it that gets used when not needed and inadvertently allowing malicious code to run on a shared folder.

Quote from ryecoaaron

The exec bit is still important for things like directories even if a filesystem is mounted noexec.

Which is a lack of my understanding of Linux, only been using it hard core for a about a year.

There needs to be a way then to distinguish between execute and execute and why if you turn off execute why you still need execute. But that is a topic outside of OMV.

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 clearly denotes only 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.

After reading some threads I found the issue and had to remove noexec. All is working
I would suggest:

• The ability to set the noexec in the GUI. Maybe in advance settings.
• If this is a security concern than express that when turning it off, removing noexec.
• Add some consistency to the sharing parts of the GUI. Some actions show execute as an option while other don't
• Check if the noexec is set and if it is set don't show execute anywhere. Otherwise add execute to the drop down options and to the grids.
• If noexec is set show a message that no executing on the share when, adding a share, changing privileges, or changing ACL

If I had some of those items above I would have clearly know what I would needed to do. I would know that out of the box OMV was not going to allow executing on a share.

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 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 will be multiple OMVs and Kubernetes!

In my case I"m using ASP.Net Core 3.0 Preview SDK in a docker container that I don't want to install on my local computer. Perfect fit for OMV!
Trying to emulate production by not having docker on my local computer.
I'm also experimenting with docker compose (.Net, RavenDB, MSSql, Vault)

Thank You