run as non-privleged

[freeagent1384]

I recognize this is not really a issue, more of a request of a feature request. I'm sure there are some very specific reasons why the container needs to run as privileged but I'm hoping there's a way to avoid this requirement or configure the host to bypass this? Even if I can just restrict the privileges granted would be a nice improvement but I don't know what to create explicate exceptions for. Any chance you can provide some insight?

[Misioslav]

To be completely honest, I never gave much thought to that. At this stage it might be a relict of the past a bit but it may depend on the usage scenario. If used just for a couple of containers it might not be required (I didn't test that theory tho). When I will have some time for some testing I can try to test out different scenarios.