Security: Authentication model

[metalivedev]

If you can manipulate docker from inside docker, what is the authentication model?
How do I keep other containers from messing with me, cloning me, starting me, stopping me?
Or how do I give them permission to do so?

[shykes]

On Thu, Jan 31, 2013 at 5:56 PM, Andy Rothfusz notifications@github.comwrote:

If you can manipulate docker from inside docker, what is the
authentication model?
How do I keep other containers from messing with me, cloning me, starting
me, stopping me?
Or how do I give them permission to do so?

When we offer an introspection API, it will have to be scoped. That can be
done by source IP for example, since Docker controls the networking
topology and addressing for all containers.

Optionally, containers could have a "privileged" flag which allows them to
mess with other containers. This would be a great way to extend the
capabilities of Docker while staying in "userland".

[shykes]

Closing the issue, feel free to continue the conversation on the mailing list.