1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00

Fixed link to kernel dependencies. Wrapped long lines. Removed old tar dependency from list.

Docker-DCO-1.1-Signed-off-by: Andy Rothfusz <github@developersupport.net> (github: metalivedev)
This commit is contained in:
Andy Rothfusz 2014-01-30 16:03:13 -08:00
parent 637a1dcab6
commit 98518bbcad

View file

@ -12,18 +12,22 @@ Binaries
**This instruction set is meant for hackers who want to try out Docker **This instruction set is meant for hackers who want to try out Docker
on a variety of environments.** on a variety of environments.**
Before following these directions, you should really check if a packaged version Before following these directions, you should really check if a
of Docker is already available for your distribution. We have packages for many packaged version of Docker is already available for your distribution.
distributions, and more keep showing up all the time! We have packages for many distributions, and more keep showing up all
the time!
Check runtime dependencies Check runtime dependencies
-------------------------- --------------------------
.. DOC COMMENT: this should be kept in sync with
https://github.com/dotcloud/docker/blob/master/hack/PACKAGERS.md#runtime-dependencies
To run properly, docker needs the following software to be installed at runtime: To run properly, docker needs the following software to be installed at runtime:
- GNU Tar version 1.26 or later - iproute2 version 3.5 or later (build after 2012-05-21), and
- iproute2 version 3.5 or later (build after 2012-05-21), and specifically the "ip" utility specifically the "ip" utility
- iptables version 1.4 or later - iptables version 1.4 or later
- The LXC utility scripts (http://lxc.sourceforge.net) version 0.8 or later - The LXC utility scripts (http://lxc.sourceforge.net) version 0.8 or later
- Git version 1.7 or later - Git version 1.7 or later
@ -33,11 +37,11 @@ To run properly, docker needs the following software to be installed at runtime:
Check kernel dependencies Check kernel dependencies
------------------------- -------------------------
Docker in daemon mode has specific kernel requirements. For details, see Docker in daemon mode has specific kernel requirements. For details,
http://docs.docker.io/en/latest/articles/kernel/ check your distribution in :ref:`installation_list`.
Note that Docker also has a client mode, which can run on virtually any linux kernel (it even builds Note that Docker also has a client mode, which can run on virtually
on OSX!). any linux kernel (it even builds on OSX!).
Get the docker binary: Get the docker binary:
@ -63,18 +67,18 @@ Run the docker daemon
Giving non-root access Giving non-root access
---------------------- ----------------------
The ``docker`` daemon always runs as the root user, and since Docker version The ``docker`` daemon always runs as the root user, and since Docker
0.5.2, the ``docker`` daemon binds to a Unix socket instead of a TCP port. By version 0.5.2, the ``docker`` daemon binds to a Unix socket instead of
default that Unix socket is owned by the user *root*, and so, by default, you a TCP port. By default that Unix socket is owned by the user *root*,
can access it with ``sudo``. and so, by default, you can access it with ``sudo``.
Starting in version 0.5.3, if you (or your Docker installer) create a Starting in version 0.5.3, if you (or your Docker installer) create a
Unix group called *docker* and add users to it, then the ``docker`` Unix group called *docker* and add users to it, then the ``docker``
daemon will make the ownership of the Unix socket read/writable by the daemon will make the ownership of the Unix socket read/writable by the
*docker* group when the daemon starts. The ``docker`` daemon must *docker* group when the daemon starts. The ``docker`` daemon must
always run as the root user, but if you run the ``docker`` client as a user in always run as the root user, but if you run the ``docker`` client as a
the *docker* group then you don't need to add ``sudo`` to all the user in the *docker* group then you don't need to add ``sudo`` to all
client commands. the client commands.
.. warning:: The *docker* group is root-equivalent. .. warning:: The *docker* group is root-equivalent.
@ -82,7 +86,8 @@ client commands.
Upgrades Upgrades
-------- --------
To upgrade your manual installation of Docker, first kill the docker daemon: To upgrade your manual installation of Docker, first kill the docker
daemon:
.. code-block:: bash .. code-block:: bash