O.S.Tezer f87a97f7df Improve code/comment/output markings & display consistency

This PR aims to increase the consistency across the docs for
code blocks and code/comment/output markings.

Rule followed here is "what's visible on the screen should be reflected"

Issue:

 - Docs had various code blocks showing: comments, commands & outputs.
 - All three of these items were inconsistently marked.

Some examples as to how this PR aims to introduce improvements:

1. Removed `> ` from in front of the "outputs". Eg,
`    > REPOSITORY                 TAG       ID              CREATED` replaced with:
`    REPOSITORY                 TAG       ID              CREATED`.

2. Introduced `$` for commands. Eg,
`    sudo chkconfig docker on` replaced with:
`    $ sudo chkconfig docker on`

3. Comments:
`    > # ` replaced with:
`    # `.

> Please note:
> Due to a vast amount of items reviewed and changed for this PR, there
> might be some individually incorrect replacements OR patterns of incorrect
> replacements. This PR needs to be reviewed and if there is anything missing,
> it should be improved or amended.

Closes:
https://github.com/dotcloud/docker/issues/5286

Docker-DCO-1.1-Signed-off-by: O.S. Tezer <ostezer@gmail.com> (github: ostezer)

2014-05-01 17:52:01 +03:00

2.9 KiB

Raw Blame History

page_title: Installation on Gentoo page_description: Please note this project is currently under heavy development. It should not be used in production. page_keywords: gentoo linux, virtualization, docker, documentation, installation

Gentoo

Note

Docker is still under heavy development! We don't recommend using it in production yet, but we're getting closer with each release. Please see our blog post, Getting to Docker 1.0

Note

This is a community contributed installation path. The only official installation is using the Ubuntu installation path. This version may be out of date because it depends on some binaries to be updated and published

Installing Docker on Gentoo Linux can be accomplished using one of two methods. The first and best way if you're looking for a stable experience is to use the official app-emulation/docker package directly in the portage tree.

If you're looking for a -bin ebuild, a live ebuild, or bleeding edge ebuild changes/fixes, the second installation method is to use the overlay provided at https://github.com/tianon/docker-overlay which can be added using app-portage/layman. The most accurate and up-to-date documentation for properly installing and using the overlay can be found in the overlay README.

Note that sometimes there is a disparity between the latest version and what's in the overlay, and between the latest version in the overlay and what's in the portage tree. Please be patient, and the latest version should propagate shortly.

Installation

The package should properly pull in all the necessary dependencies and prompt for all necessary kernel options. The ebuilds for 0.7+ include use flags to pull in the proper dependencies of the major storage drivers, with the "device-mapper" use flag being enabled by default, since that is the simplest installation path.

$ sudo emerge -av app-emulation/docker

If any issues arise from this ebuild or the resulting binary, including and especially missing kernel configuration flags and/or dependencies, open an issue on the docker-overlay repository or ping tianon directly in the #docker IRC channel on the freenode network.

Starting Docker

Ensure that you are running a kernel that includes all the necessary modules and/or configuration for LXC (and optionally for device-mapper and/or AUFS, depending on the storage driver you`ve decided to use).

OpenRC

To start the docker daemon:

$ sudo /etc/init.d/docker start

To start on system boot:

$ sudo rc-update add docker default

systemd