Timothy Hobbs

They all do, pretty much. Permissions are granted by passing arguments to Docker, and the runtime file builds that list of arguments. https://github.com/subuser-security/subuser/blob/master/logic/subuserlib/classes/subuserSubmodules/run/runtime.py#L108 getPermissionsFlagDict is the most important one though....

What are you trying to do?

Permissions are granted when the subuser is started. So that message box would appear when you launch the subuser, not when the permission is needed. On 04/12/16 14:43, Suici Doga...

Unfortunately, so long as we use Docker, which doesn't allow for changing container permissions after launch, this isn't possible. Once the move to runc takes place many previously impossible things...

@SuicSoft there have been many issues about this open(or closed) for years: - https://github.com/docker/docker/issues/9849 - https://github.com/docker/docker/issues/2045 - https://github.com/docker/docker/issues/3285 The list goes on...

I believe that you are refering to "only through the API, as you can pass bind-mounts and volumes-from on start." But this doesn't allow for modifying RUNNING containers, it only...

You're making a joke about beurocracy, right? ;)

@SuicSoft yes, in the future, subuser will not use Docker and things will move along more quickly, be better, and break less often.

The 0.5 line uses Docker, the 0.6 line will use runc. However, there are still a lot of pre-requisits that I want to get down before I can start working...

Like with the `docker pull` command instead of building the images.