InformationUse native Docker authorization plugins or a third party authorization mechanism with Docker daemon to manage access to Docker client commands.
Dockers out-of-the-box authorization model is all or nothing. Any user with permission to access the Docker daemon can run any Docker client command. The same is true for callers using Dockers remote API to contact the daemon. If you require greater access control, you can create authorization plugins and add them to your Docker daemon configuration. Using an authorization plugin, a Docker administrator can configure granular access policies for managing access to Docker daemon.
Third party integrations of Docker may implement their own authorization models to require authorization with the Docker daemon outside of docker's native authorization plugin (i.e. Kubernetes, Cloud Foundry, Openshift).
SolutionStep 1: Install/Create an authorization plugin.
Step 2: Configure the authorization policy as desired.
Step 3: Start the docker daemon as below:
Each docker command specifically passes through authorization plugin mechanism. This might introduce a slight performance drop.
Third party use of alternative container engines that utilize the docker daemon may provide alternative mechanisms to provide this security control.
By default, authorization plugins are not set up.