blob: 93cf966c44c4a391e26c65b03626fd794dcf8607 (
plain)
1 Kernel Requirements
2 ===================
3
4 If you want to have a full working CRUX+Docker system you will need to
5 rebuild your kernel and enable various networking, cgroups
6 and optional lvm options
7
8 You may check your kernel configuration by running:
9
10 ::
11
12 /usr/share/docker/check-config.sh
13
14 .. note:: If you receive an error such as "cgroup hierarchy: nonexistent??"
15 then you should run ``cgroupfs-mount`` and re-run
16 ``/usr/share/docker/check-config.sh``.
17
18 Please follow the guideance of the output of
19 ``/usr/share/docker/check-config.sh`` carefully.
20
21
22 Execution Engines
23 =================
24
25 As of Docker 0.9+ execution engines are pluggable and as such Docker
26 no longer depends on lxc.
27
28 The new default execution driver is now an internal ``libcontainer``
29 driver that replaces the need for lxc.
30
31 Please see the `Docker Documentation <http://docs.docker.io>`_
32 if you want to use a different execution engine other then the default.
33
34
35 Storage Backends
36 ================
37
38 Docker comes with three main Storage Backends:
39
40 - AUFS (*requires AUFS kernel/patches*)
41 - devmapper
42 - btrfs
43
44 It is recommended you use the devmapper or btrfs backend (Default: devmapper).
45
46 To use the ``btrfs`` backend edit ``/etc/docker.conf``
47 and modify the ``DOCKER_OPTS`` with:
48
49 ::
50
51 DOCKER_OPTS="-s btrfs"
52
53 .. note:: As of Docker 0.10.x the ``btrfs`` storage backend is now
54 considered stable and has been promoted to an officially
55 supported storage backend.
56
57
58 Docker Client
59 =============
60
61 Add yourself to the ``docker`` group if you wish to access
62 the Docker daemon on localhost via UNIX Socket.
|
