From c79c5213b21eb16a3f7f2039e471cd79a03d8051 Mon Sep 17 00:00:00 2001 From: Deni Bertovic Date: Wed, 21 Aug 2013 17:28:13 +0200 Subject: [PATCH] small fix to docs regarding adding docker groups Upstream-commit: 467dbb75f10ae97e785a127a7547a5015cbb2a99 Component: engine --- components/engine/docs/sources/use/basics.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/components/engine/docs/sources/use/basics.rst b/components/engine/docs/sources/use/basics.rst index 411e1c30d1..eef6740599 100644 --- a/components/engine/docs/sources/use/basics.rst +++ b/components/engine/docs/sources/use/basics.rst @@ -41,7 +41,7 @@ Why ``sudo``? The ``docker`` daemon always runs as root, and since ``docker`` version 0.5.2, ``docker`` binds to a Unix socket instead of a TCP port. By default that Unix socket is owned by the user *root*, and so, -by default, you can access it with ``sudo``. +by default, you can access it with ``sudo``. Starting in version 0.5.3, if you create a Unix group called *docker* and add users to it, then the ``docker`` daemon will make the @@ -56,6 +56,8 @@ you don't need to add ``sudo`` to all the client commands. sudo groupadd docker # Add the ubuntu user to the docker group + # You may have to logout and log back in again for + # this to take effect sudo gpasswd -a ubuntu docker # Restart the docker daemon