Answers: <p>Hi and welcome to DevOps SE!</p>
  
  <p>To enable Role-Based Access Control (<a href="https://en.wikipedia.org/wiki/Role-based_access_control" rel="nofollow noreferrer">RBAC</a>) for Docker Engine, you need the UCP (Universal Control Pane) available through Docker EE. </p>
  
  <p><a href="https://success.docker.com/article/rbac-example-overview" rel="nofollow noreferrer">https://success.docker.com/article/rbac-example-overview</a></p>
  
  <p>A free alternative could be also the Kubernetes module <strong><em><a href="https://kubernetes.io/docs/reference/access-authn-authz/rbac/" rel="nofollow noreferrer">rbac.authorization.k8s.io</a></em></strong>.</p>
  
  <p>Side note: To control docker commands available to a user, use <strong><em>AuthZPlugin</em></strong> for the Docker engine (there are open source implementations of this <a href="https://docs.docker.com/engine/extend/plugins_authorization/" rel="nofollow noreferrer">API</a>). </p>
  
Answers: CC BY-SA 4.0
Answers: 2018-09-13T08:03:59.823Z
Answers: I've read the documentation, but I am still not sure, how this can be done. Would you be able to add some example to your answer?
Answers: noisy
Answers: CC BY-SA 4.0
Answers: 2018-09-13T08:11:24.150Z
Answers: it looks like, with both solutions I can only restrict a users access to particular commands. But what I need, is to give full access to some container and none access to others
Answers: noisy
Answers: CC BY-SA 4.0
Answers: 2018-09-13T08:22:58.953Z
Answers: yeah...at first glance, this is what I need. But pricing of docker EE...is not acceptable for me :(
Answers: noisy
Answers: CC BY-SA 4.0
Answers: 2018-09-13T07:51:46.023Z
Answers: 2018-09-13T11:09:30.383Z
Answers: 2018-09-13T11:09:30.383Z
Answers: Ta Mu
Body: <p>I want to use one server to host multiple docker-containers. I want to give another user a possibility to manage new docker-containers, but I do not want to give him access to all other containers, which I started, since they may contain sensitive data.</p>
  
  <p>Is there a way to create a secure configuration which doesn't require creating virtual machine?</p>
  
Tags: <docker><virtualization><role-based-access-control>
Title: Do not show all docker containers to a particular user
UserDisplayName: noisy
ThreadText: # Do not show all docker containers to a particular user
  
  (Asked by: username_0 on 2018-09-13)
  
  I want to use one server to host multiple docker-containers. I want to give another user a possibility to manage new docker-containers, but I do not want to give him access to all other containers, which I started, since they may contain sensitive data.
  
  Is there a way to create a secure configuration which doesn't require creating virtual machine?
  
  **Tags:** docker, virtualization, role-based-access-control
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-09-13. Score: 1
  
  Hi and welcome to DevOps SE!
  
  To enable Role-Based Access Control ([RBAC](https://en.wikipedia.org/wiki/Role-based_access_control)) for Docker Engine, you need the UCP (Universal Control Pane) available through Docker EE.
  
  <https://success.docker.com/article/rbac-example-overview>
  
  A free alternative could be also the Kubernetes module ***[rbac.authorization.k8s.io](https://kubernetes.io/docs/reference/access-authn-authz/rbac/)***.
  
  Side note: To control docker commands available to a user, use ***AuthZPlugin*** for the Docker engine (there are open source implementations of this [API](https://docs.docker.com/engine/extend/plugins_authorization/)).
  
  > **Comments:**
  > **username_0**: I've read the documentation, but I am still not sure, how this can be done. Would you be able to add some example to your answer?  
  > **username_0**: it looks like, with both solutions I can only restrict a users access to particular commands. But what I need, is to give full access to some container and none access to others  
  > **username_0**: yeah...at first glance, this is what I need. But pricing of docker EE...is not acceptable for me :(  
  
  ---
  
  