This is an RFE from talking with customers at Container Con.


During Container Con, Docker presented the ability to sign docker images and thus allow a user to trust that an image is valid. In this same vein rkt demonstrated similar capabilities and spoke about how they are looking to expand this to allow/disallow certain actions based on the level of trust given to a particular key.

Docker should provide this kind of control as well. 

For example, if an image was signed with key A that the user trusts for network operations, but not for storage operations then docker could be configured to refuse to start a container if the user was trying to volume-mount something into the container. However, if the image was signed with key B that the user "trusts more", then docker would allow the volume-mount.