mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
122 lines
3.5 KiB
ReStructuredText
122 lines
3.5 KiB
ReStructuredText
:title: Installation from Binaries
|
|
:description: This instruction set is meant for hackers who want to try out Docker on a variety of environments.
|
|
:keywords: binaries, installation, docker, documentation, linux
|
|
|
|
.. _binaries:
|
|
|
|
Binaries
|
|
========
|
|
|
|
.. include:: install_header.inc
|
|
|
|
**This instruction set is meant for hackers who want to try out Docker
|
|
on a variety of environments.**
|
|
|
|
Before following these directions, you should really check if a
|
|
packaged version of Docker is already available for your distribution.
|
|
We have packages for many distributions, and more keep showing up all
|
|
the time!
|
|
|
|
|
|
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:
|
|
|
|
- iptables version 1.4 or later
|
|
- Git version 1.7 or later
|
|
- XZ Utils 4.9 or later
|
|
- a `properly mounted
|
|
<https://github.com/tianon/cgroupfs-mount/blob/master/cgroupfs-mount>`_
|
|
cgroupfs hierarchy (having a single, all-encompassing "cgroup" mount point `is
|
|
<https://github.com/dotcloud/docker/issues/2683>`_ `not
|
|
<https://github.com/dotcloud/docker/issues/3485>`_ `sufficient
|
|
<https://github.com/dotcloud/docker/issues/4568>`_)
|
|
|
|
|
|
Check kernel dependencies
|
|
-------------------------
|
|
|
|
Docker in daemon mode has specific kernel requirements. For details,
|
|
check your distribution in :ref:`installation_list`.
|
|
|
|
In general, a 3.8 Linux kernel (or higher) is preferred, as some of the
|
|
prior versions have known issues that are triggered by Docker.
|
|
|
|
Note that Docker also has a client mode, which can run on virtually
|
|
any Linux kernel (it even builds on OSX!).
|
|
|
|
|
|
Get the docker binary:
|
|
----------------------
|
|
|
|
.. code-block:: bash
|
|
|
|
wget https://get.docker.io/builds/Linux/x86_64/docker-latest -O docker
|
|
chmod +x docker
|
|
|
|
.. note::
|
|
If you have trouble downloading the binary, you can also get the smaller
|
|
compressed release file: https://get.docker.io/builds/Linux/x86_64/docker-latest.tgz
|
|
|
|
Run the docker daemon
|
|
---------------------
|
|
|
|
.. code-block:: bash
|
|
|
|
# start the docker in daemon mode from the directory you unpacked
|
|
sudo ./docker -d &
|
|
|
|
|
|
.. _dockergroup:
|
|
|
|
Giving non-root access
|
|
----------------------
|
|
|
|
The ``docker`` daemon always runs as the root user, and since Docker
|
|
version 0.5.2, the ``docker`` daemon 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``.
|
|
|
|
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``
|
|
daemon will make the ownership of the Unix socket read/writable by the
|
|
*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 the *docker* group then you don't need to add ``sudo`` to all
|
|
the client commands.
|
|
|
|
.. warning:: The *docker* group (or the group specified with ``-G``) is
|
|
root-equivalent; see :ref:`dockersecurity_daemon` details.
|
|
|
|
|
|
Upgrades
|
|
--------
|
|
|
|
To upgrade your manual installation of Docker, first kill the docker
|
|
daemon:
|
|
|
|
.. code-block:: bash
|
|
|
|
killall docker
|
|
|
|
Then follow the regular installation steps.
|
|
|
|
|
|
Run your first container!
|
|
-------------------------
|
|
|
|
.. code-block:: bash
|
|
|
|
# check your docker version
|
|
sudo ./docker version
|
|
|
|
# run a container and open an interactive shell in the container
|
|
sudo ./docker run -i -t ubuntu /bin/bash
|
|
|
|
|
|
|
|
Continue with the :ref:`hello_world` example.
|