docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Simplify install instructions now that our overlay is in the official repositories.xml list, and add note about hacky #1422 workaround

This commit is contained in:
Tianon Gravi 2013-09-19 11:49:43 -06:00
parent 77ad95d372
commit 341addeccd
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/sources/installation/gentoolinux.rst
View File

@ -25,15 +25,11 @@ Ensure that layman is installed:
sudo emerge -av app-portage/layman sudo emerge -av app-portage/layman
Using your favorite editor, add Add the "docker" overlay using layman:
``https://raw.github.com/tianon/docker-overlay/master/repositories.xml`` to the
``overlays`` section in ``/etc/layman/layman.cfg`` (as per instructions on the
`Gentoo Wiki <http://wiki.gentoo.org/wiki/Layman#Adding_custom_overlays>`_),
then invoke the following:
.. code-block:: bash .. code-block:: bash
sudo layman -f -a docker sudo layman -a docker
Once that completes, the ``app-emulation/docker`` package will be available Once that completes, the ``app-emulation/docker`` package will be available
for emerge: for emerge:
@ -44,7 +40,7 @@ for emerge:
If you prefer to use the official binaries, or just do not wish to compile If you prefer to use the official binaries, or just do not wish to compile
docker, emerge ``app-emulation/docker-bin`` instead. It is important to docker, emerge ``app-emulation/docker-bin`` instead. It is important to
remember that Gentoo is still an unsupported platform, even when using the remember that Gentoo is still an unofficial platform, even when using the
official binaries. official binaries.
The package should already include all the necessary dependencies. For the The package should already include all the necessary dependencies. For the
@ -123,3 +119,7 @@ Unfortunately, Gentoo suffers from `issue #1422
fresh start of docker, the first docker run fails due to some tricky terminal fresh start of docker, the first docker run fails due to some tricky terminal
issues, so be sure to run something trivial (such as ``docker run -i -t busybox issues, so be sure to run something trivial (such as ``docker run -i -t busybox
echo hi``) before attempting to run anything important. echo hi``) before attempting to run anything important.
There is a tentative (and very hacky) workaround for this in the OpenRC init
script, and it can be enabled by modifying the appropriate value in
``/etc/conf.d/docker`` after successful installation.