1. docker
  2. Commit f9ab04ad13863fca6e7b0f3d519dc9e0b08fc567
Browse code

First pass of updates Working docs Update after check update to centos 7 after second test Updating with hopefully correct urls Adding thaJetzah's comments Updating with the new images Updating after a visual check

Signed-off-by: Mary Anthony <mary@docker.com>

Updating with comments

Signed-off-by: Mary Anthony <mary@docker.com>

Mary Anthony authored on 2015/05/12 03:32:05
Showing 3 changed files
docs/installation/centos.md
History View file @ f9ab04a
... ... 
@@ -12,153 +12,185 @@ parent = "smn_linux"
12 12
13 13 
 Docker is supported on the following versions of CentOS:
14 14
15 
-- [*CentOS 7 (64-bit)*](#installing-docker-centos-7)
16 
-- [*CentOS 6.5 (64-bit)*](#installing-docker-centos-6.5) or later
15 
+* CentOS 7.X
16 
+* CentOS 6.5 or higher
17 
+
18 
+Installation on other binary compatible EL6/EL7 distributions such as Scientific
19 
+Linux might succeed, but Docker does not test or support Docker on these
20 
+distributions.
21 
+
22 
+This page instructs you to install using Docker-managed release packages and
23 
+installation mechanisms. Using these packages ensures you get the latest release
24 
+of Docker. If you wish to install using CentOS-managed packages, consult your
25 
+CentOS documentation.
26 
+
27 
+## Prerequisites
28 
+
29 
+Docker requires a 64-bit installation regardless of your CentOS version. Also,
30 
+your kernel must be 3.10 at minimum. CentOS 7 runs the 3.10 kernel, 6.5 does
31 
+not. We make an exception for CentOS 6.5. To run Docker on
32 
+[CentOS-6.5](https://www.centos.org) or later, you need kernel 2.6.32-431 or
33 
+higher.
34 
+
35 
+To check your current kernel version, open a terminal and use `uname -r` to
36 
+display your kernel version:
37 
+
38 
+    $ uname -r
39 
+    2.6.32-431.el6.x86_64
40 
+
41 
+Finally, is it recommended that you fully update your system. Please keep in
42 
+mind that CentOS 6 should be fully patched to fix any potential kernel bugs. Any
43 
+reported kernel bugs may have already been fixed on the latest kernel packages
44 
+
45 
+## Install
46 
+
47 
+You use the same installation procedure for all versions of CentOS,
48 
+only the package you install differs. There are two packages to choose from:
49 
+
50 
+<table>
51 
+  <tr>
52 
+    <th>Version</th>
53 
+    <th>Package name</th>
54 
+  </tr>
55 
+  <tr>
56 
+    <td>6.5 and  higher</td>
57 
+    <td>
58 
+    <p>
59 
+    <a href="https://get.docker.com/rpm/1.7.0/centos-6/RPMS/x86_64/docker-engine-1.7.0-1.el6.x86_64.rpm">
60 
+    https://get.docker.com/rpm/1.7.0/centos-6/RPMS/x86_64/docker-engine-1.7.0-1.el6.x86_64.rpm</a>
61 
+    <p>
62 
+    <a href="https://get.docker.com/rpm/1.7.0/centos-6/SRPMS/docker-engine-1.7.0-1.el6.src.rpm">
63 
+   https://get.docker.com/rpm/1.7.0/centos-6/SRPMS/docker-engine-1.7.0-1.el6.src.rpm</a>
64 
+    <p>
65 
+    </p>
66 
+    </td>
67 
+  </tr>
68 
+  <tr>
69 
+    <td>7.X</td>
70 
+    <td>
71 
+    <p>
72 
+     <a href="https://get.docker.com/rpm/1.7.0/centos-7/RPMS/x86_64/docker-engine-1.7.0-1.el7.centos.x86_64.rpm">
73 
+    https://get.docker.com/rpm/1.7.0/centos-7/RPMS/x86_64/docker-engine-1.7.0-1.el7.centos.x86_64.rpm</a>
74 
+    </p>
75 
+    <p>
76 
+     <a href="https://get.docker.com/rpm/1.7.0/centos-7/SRPMS/docker-engine-1.7.0-1.el7.centos.src.rpm">
77 
+    https://get.docker.com/rpm/1.7.0/centos-7/SRPMS/docker-engine-1.7.0-1.el7.centos.src.rpm</a>
78 
+    </p>
79 
+    </td>
80 
+  </tr>
81 
+</table>
17 82
18 
-These instructions are likely work for other binary compatible EL6/EL7 distributions
19 
-such as Scientific Linux, but they haven't been tested.
20 83
21 
-Please note that due to the current Docker limitations, Docker is able to
22 
-run only on the **64 bit** architecture.
84 
+This procedure depicts an installation on version 6.5. If you are installing on
85 
+7.X, substitute that package for your installation.
23 86
24 
-## Kernel support
87 
+1. Log into your machine as a user with `sudo` or `root` privileges.
25 88
26 
-Currently the CentOS project will only support Docker when running on kernels
27 
-shipped by the distribution. There are kernel changes which will cause issues
28 
-if one decides to step outside that box and run non-distribution kernel packages.
89 
+2. Make sure your existing packages are up-to-date.
29 90
30 
-To run Docker on [CentOS-6.5](http://www.centos.org) or later, you will need
31 
-kernel version 2.6.32-431 or higher as this has specific kernel fixes to allow
32 
-Docker to run.
91 
+		$ sudo yum update
92 
+
93 
+3. Download the Docker RPM to the current directory.
94 
+
95 
+		$ curl -O -sSL https://get.docker.com/rpm/1.7.0/centos-6/RPMS/x86_64/docker-engine-1.7.0-1.el6.x86_64.rpm
33 96
34 
-## CentOS-7
97 
+4. Use `yum` to install the package.
35 98
36 
-### Installation
99 
+		$ sudo yum localinstall --nogpgcheck docker-engine-1.7.0-1.el6.x86_64.rpm
37 100
38 
-Docker is included by default in the CentOS-Extras repository. To install
39 
-run the following command:
101 
+5. Start the Docker daemon.
40 102
41 
-    $ sudo yum install docker
103 
+		$ sudo service docker start
42 104
43 
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
105 
+6. Verify `docker` is installed correctly by running a test image in a container.
44 106
45 
-### Uninstallation
107 
+		$ sudo docker run hello-world
108 
+		Unable to find image 'hello-world:latest' locally
109 
+		latest: Pulling from hello-world
110 
+		a8219747be10: Pull complete
111 
+		91c95931e552: Already exists
112 
+		hello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
113 
+		Digest: sha256:aa03e5d0d5553b4c3473e89c8619cf79df368babd1.7.0cf5daeb82aab55838d
114 
+		Status: Downloaded newer image for hello-world:latest
115 
+		Hello from Docker.
116 
+		This message shows that your installation appears to be working correctly.
46 117
47 
-To uninstall the Docker package:
118 
+		To generate this message, Docker took the following steps:
119 
+		 1. The Docker client contacted the Docker daemon.
120 
+		 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
121 
+				(Assuming it was not already locally available.)
122 
+		 3. The Docker daemon created a new container from that image which runs the
123 
+				executable that produces the output you are currently reading.
124 
+		 4. The Docker daemon streamed that output to the Docker client, which sent it
125 
+				to your terminal.
48 126
49 
-    $ sudo yum -y remove docker
127 
+		To try something more ambitious, you can run an Ubuntu container with:
128 
+		 $ docker run -it ubuntu bash
129 
+
130 
+		For more examples and ideas, visit:
131 
+		 http://docs.docker.com/userguide/
132 
+
133 
+## Create a docker group
50 134
51 
-The above command will not remove images, containers, volumes, or user created
52 
-configuration files on your host. If you wish to delete all images, containers,
53 
-and volumes run the following command:
135 
+The `docker` daemon binds to a Unix socket instead of a TCP port. By default
136 
+that Unix socket is owned by the user `root` and other users can access it with
137 
+`sudo`. For this reason, `docker` daemon always runs as the `root` user.
54 138
55 
-    $ rm -rf /var/lib/docker
139 
+To avoid having to use `sudo` when you use the `docker` command, create a Unix
140 
+group called `docker` and add users to it. When the `docker` daemon starts, it
141 
+makes the ownership of the Unix socket read/writable by the `docker` group.
56 142
57 
-You must delete the user created configuration files manually.
143 
+>**Warning**: The `docker` group is equivalent to the `root` user; For details
144 
+>on how this impacts security in your system, see [*Docker Daemon Attack
145 
+>Surface*](/articles/security/#docker-daemon-attack-surface) for details.
58 146
59 
-## CentOS-6.5
147 
+To create the `docker` group and add your user:
148 
+
149 
+1. Log into Centos as a user with `sudo` privileges.
150 
+
151 
+2. Create the `docker` group and add your user.
152 
+
153 
+    `sudo usermod -aG docker your_username`
60 154
61 
-### Installation
155 
+3. Log out and log back in.
62 156
63 
-For CentOS-6.5, the Docker package is part of [Extra Packages
64 
-for Enterprise Linux (EPEL)](https://fedoraproject.org/wiki/EPEL) repository,
65 
-a community effort to create and maintain additional packages for the RHEL distribution.
157 
+    This ensures your user is running with the correct permissions.
66 158
67 
-Firstly, you need to ensure you have the EPEL repository enabled. Please
68 
-follow the [EPEL installation instructions](
69 
-https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F).
159 
+4. Verify your work by running `docker` without `sudo`.
70 160
71 
-For CentOS-6, there is a package name conflict with a system tray application
72 
-and its executable, so the Docker RPM package was called `docker-io`.
161 
+		$ docker run hello-world
162 
+
163 
+## Start the docker daemon at boot
73 164
74 
-To proceed with `docker-io` installation on CentOS-6, you may need to remove the
75 
-`docker` package first.
165 
+To ensure Docker starts when you boot your system, do the following:
76 166
77 
-    $ sudo yum -y remove docker
167 
+      $ sudo chkconfig docker on
78 168
79 
-Next, let's install the `docker-io` package which will install Docker on our host.
80 
-
81 
-    $ sudo yum install docker-io
82 
-
83 
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
84 
-
85 
-### Uninstallation
86 
-
87 
-To uninstall the Docker package:
88 
-
89 
-    $ sudo yum -y remove docker-io
90 
-
91 
-The above command will not remove images, containers, volumes, or user created
92 
-configuration files on your host. If you wish to delete all images, containers,
93 
-and volumes run the following command:
94 
-
95 
-    $ rm -rf /var/lib/docker
96 
-
97 
-You must delete the user created configuration files manually.
98 
-
99 
-## Manual installation of latest Docker release
100 
-
101 
-While using a package is the recommended way of installing Docker,
102 
-the above package might not be the current release version. If you need the latest
103 
-version, [you can install the binary directly](
104 
-https://docs.docker.com/installation/binaries/).
105 
-
106 
-When installing the binary without a package, you may want
107 
-to integrate Docker with Systemd. For this, install the two unit files
108 
-(service and socket) from [the GitHub
109 
-repository](https://github.com/docker/docker/tree/master/contrib/init/systemd)
110 
-to `/etc/systemd/system`.
111 
-
112 
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
113 
-
114 
-## Starting the Docker daemon
115 
-
116 
-Once Docker is installed, you will need to start the docker daemon.
117 
-
118 
-    $ sudo service docker start
119 
-
120 
-If we want Docker to start at boot, we should also:
121 
-
122 
-    $ sudo chkconfig docker on
123 
-
124 
-Now let's verify that Docker is working. First we'll need to get the latest
125 
-`centos` image.
126 
-
127 
-    $ sudo docker pull centos
128 
-
129 
-Next we'll make sure that we can see the image by running:
130 
-
131 
-    $ sudo docker images centos
169 
+If you need to add an HTTP Proxy, set a different directory or partition for the
170 
+Docker runtime files, or make other customizations, read our Systemd article to
171 
+learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
132 172
133 
-This should generate some output similar to:
134 173
135 
-    $ sudo docker images centos
136 
-    REPOSITORY      TAG             IMAGE ID          CREATED             VIRTUAL SIZE
137 
-    centos          latest          0b443ba03958      2 hours ago         297.6 MB
174 
+## Uninstall
138 175
139 
-Run a simple bash shell to test the image:
176 
+You can uninstall the Docker software with `yum`.
140 177
141 
-    $ sudo docker run -i -t centos /bin/bash
178 
+1. List the package you have installed.
142 179
143 
-If everything is working properly, you'll get a simple bash prompt. Type
144 
-`exit` to continue.
180 
+		$ yum list installed | grep docker
181 
+		yum list installed | grep docker
182 
+		docker-engine.x86_64                1.7.0-1.el6
183 
+																																								 @/docker-engine-1.7.0-1.el6.x86_64.rpm
145 184
146 
-## Custom daemon options
185 
+2. Remove the package.
147 186
148 
-If you need to add an HTTP Proxy, set a different directory or partition for the
149 
-Docker runtime files, or make other customizations, read our Systemd article to
150 
-learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
187 
+		$ sudo yum -y remove docker-engine.x86_64
151 188
152 
-## Dockerfiles
153 
-The CentOS Project provides a number of sample Dockerfiles which you may use
154 
-either as templates or to familiarize yourself with docker. These templates
155 
-are available on GitHub at [https://github.com/CentOS/CentOS-Dockerfiles](
156 
-https://github.com/CentOS/CentOS-Dockerfiles)
189 
+	This command does not remove images, containers, volumes, or user-created
190 
+	configuration files on your host.
157 191
158 
-**Done!** You can either continue with the [Docker User
159 
-Guide](/userguide/) or explore and build on the images yourself.
192 
+3. To delete all images, containers, and volumes, run the following command:
160 193
161 
-## Issues?
194 
+		$ rm -rf /var/lib/docker
162 195
163 
-If you have any issues - please report them directly in the
164 
-[CentOS bug tracker](http://bugs.centos.org).
196 
+4. Locate and delete any user-created configuration files.
165 197 
\ No newline at end of file
docs/installation/fedora.md
History View file @ f9ab04a
... ... 
@@ -12,111 +12,221 @@ parent = "smn_linux"
12 12
13 13 
 Docker is supported on the following versions of Fedora:
14 14
15 
-- [*Fedora 20 (64-bit)*](#fedora-20-installation)
16 
-- [*Fedora 21 and later (64-bit)*](#fedora-21-and-later-installation)
15 
+- Fedora 20
16 
+- Fedora 21
17 
+- Fedora 22
18 
+
19 
+This page instructs you to install using Docker-managed release packages and
20 
+installation mechanisms. Using these packages ensures you get the latest release
21 
+of Docker. If you wish to install using Fedora-managed packages, consult your
22 
+Fedora release documentation for information on Fedora's Docker support.
23 
+
24 
+##Prerequisites
25 
+
26 
+Docker requires a 64-bit installation regardless of your Fedora version. Also, your kernel must be 3.10 at minimum. To check your current kernel
27 
+version, open a terminal and use `uname -r` to display your kernel version:
28 
+
29 
+    $ uname -r
30 
+    3.19.5-100.fc20.x86_64
31 
+
32 
+If your kernel is at a older version, you must update it.
33 
+
34 
+Finally, is it recommended that you fully update your system. Please keep in
35 
+mind that your system should be fully patched to fix any potential kernel bugs. Any
36 
+reported kernel bugs may have already been fixed on the latest kernel packages
37 
+
38 
+
39 
+## Install
40 
+
41 
+You use the same installation procedure for all versions of Fedora,
42 
+only the package you install differs. There are two packages to choose from:
43 
+
44 
+<table>
45 
+  <tr>
46 
+    <th>Version</th>
47 
+    <th>Package name</th>
48 
+  </tr>
49 
+  <tr>
50 
+    <td>Fedora 20</td>
51 
+    <td>
52 
+    <p>
53 
+    <a href="https://get.docker.com/rpm/1.7.0/fedora-20/RPMS/x86_64/docker-engine-1.7.0-1.fc20.x86_64.rpm">
54 
+    https://get.docker.com/rpm/1.7.0/fedora-20/RPMS/x86_64/docker-engine-1.7.0-1.fc20.x86_64.rpm</a>
55 
+        </p>
56 
+    </td>
57 
+        <p>
58 
+    <a href="https://get.docker.com/rpm/1.7.0/fedora-20/SRPMS/docker-engine-1.7.0-1.fc20.src.rpm">
59 
+    https://get.docker.com/rpm/1.7.0/fedora-20/SRPMS/docker-engine-1.7.0-1.fc20.src.rpm/a>
60 
+        </p>
61 
+    </td>
62 
+  </tr>
63 
+  <tr>
64 
+    <td>Fedora 21</td>
65 
+    <td>
66 
+    <p>
67 
+    <a href="https://get.docker.com/rpm/1.7.0/fedora-21/RPMS/x86_64/docker-engine-1.7.0-1.fc21.x86_64.rpm">
68 
+    https://get.docker.com/rpm/1.7.0/fedora-21/RPMS/x86_64/docker-engine-1.7.0-1.fc21.x86_64.rpm</a>
69 
+        </p>
70 
+    </td>
71 
+        <p>
72 
+    <a href="https://get.docker.com/rpm/1.7.0/fedora-21/SRPMS/docker-engine-1.7.0-1.fc21.src.rpm">
73 
+    https://get.docker.com/rpm/1.7.0/fedora-21/SRPMS/docker-engine-1.7.0-1.fc21.src.rpm/a>
74 
+        </p>
75 
+    </td>
76 
+  </tr>
77 
+   <tr>
78 
+    <td>Fedora 22</td>
79 
+    <td>
80 
+    <p>
81 
+    <a href="https://get.docker.com/rpm/1.7.0/fedora-22/RPMS/x86_64/docker-engine-1.7.0-1.fc22.x86_64.rpm">
82 
+    https://get.docker.com/rpm/1.7.0/fedora-22/RPMS/x86_64/docker-engine-1.7.0-1.fc22.x86_64.rpm</a>
83 
+        </p>
84 
+    </td>
85 
+        <p>
86 
+    <a href="https://get.docker.com/rpm/1.7.0/fedora-22/SRPMS/docker-engine-1.7.0-1.fc22.src.rpm">
87 
+    https://get.docker.com/rpm/1.7.0/fedora-22/SRPMS/docker-engine-1.7.0-1.fc22.src.rpm/a>
88 
+        </p>
89 
+    </td>
90 
+  </tr>
91 
+</table>
92 
+
93 
+
94 
+This procedure depicts an installation on version 21. If you are installing on
95 
+20 or 22, substitute that package for your installation.
96 
+
97 
+1. Log into your machine as a user with `sudo` or `root` privileges.
98 
+
99 
+2. Make sure you don't have an older version of Docker installed.
100 
+
101 
+		$ yum list installed | grep docker
102 
+
103 
+	If you have an older version, remove it using the `yum -y remove <packagename>` command.
104 
+
105 
+3. Download the Docker RPM to the current directory.
106 
+
107 
+		$ curl -O -sSL https://url_to_package/docker-engine-1.7.0-0.1.fc21.x86_64.rpm
108 
+
109 
+4. Use `yum` to install the package.
110 
+
111 
+		$ sudo yum localinstall --nogpgcheck docker-engine-1.7.0-0.1.fc21.x86_64.rpm
112 
+
113 
+5. Start the Docker daemon.
114 
+
115 
+		$ sudo service docker start
116 
+
117 
+6. Verify `docker` is installed correctly by running a test image in a container.
118 
+
119 
+		$ sudo docker run hello-world
120 
+		Unable to find image 'hello-world:latest' locally
121 
+		latest: Pulling from hello-world
122 
+		a8219747be10: Pull complete
123 
+		91c95931e552: Already exists
124 
+		hello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
125 
+		Digest: sha256:aa03e5d0d5553b4c3473e89c8619cf79df368babd18681cf5daeb82aab55838d
126 
+		Status: Downloaded newer image for hello-world:latest
127 
+		Hello from Docker.
128 
+		This message shows that your installation appears to be working correctly.
129 
+
130 
+		To generate this message, Docker took the following steps:
131 
+		 1. The Docker client contacted the Docker daemon.
132 
+		 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
133 
+				(Assuming it was not already locally available.)
134 
+		 3. The Docker daemon created a new container from that image which runs the
135 
+				executable that produces the output you are currently reading.
136 
+		 4. The Docker daemon streamed that output to the Docker client, which sent it
137 
+				to your terminal.
138 
+
139 
+		To try something more ambitious, you can run an Ubuntu container with:
140 
+		 $ docker run -it ubuntu bash
141 
+
142 
+		For more examples and ideas, visit:
143 
+		 http://docs.docker.com/userguide/
144 
+
145 
+## Create a docker group
146 
+
147 
+The `docker` daemon binds to a Unix socket instead of a TCP port. By default
148 
+that Unix socket is owned by the user `root` and other users can access it with
149 
+`sudo`. For this reason, `docker` daemon always runs as the `root` user.
150 
+
151 
+To avoid having to use `sudo` when you use the `docker` command, create a Unix
152 
+group called `docker` and add users to it. When the `docker` daemon starts, it
153 
+makes the ownership of the Unix socket read/writable by the `docker` group.
154 
+
155 
+>**Warning**: The `docker` group is equivalent to the `root` user; For details
156 
+>on how this impacts security in your system, see [*Docker Daemon Attack
157 
+>Surface*](/articles/security/#docker-daemon-attack-surface) for details.
158 
+
159 
+To create the `docker` group and add your user:
160 
+
161 
+1. Log into your system as a user with `sudo` privileges.
162 
+
163 
+2. Create the `docker` group and add your user.
164 
+
165 
+    `sudo usermod -aG docker your_username`
166 
+
167 
+3. Log out and log back in.
168 
+
169 
+    This ensures your user is running with the correct permissions.
170 
+
171 
+4. Verify your work by running `docker` without `sudo`.
172 
+
173 
+        $ docker run hello-world
174 
+				Unable to find image 'hello-world:latest' locally
175 
+				latest: Pulling from hello-world
176 
+				a8219747be10: Pull complete
177 
+				91c95931e552: Already exists
178 
+				hello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
179 
+				Digest: sha256:aa03e5d0d5553b4c3473e89c8619cf79df368babd18681cf5daeb82aab55838d
180 
+				Status: Downloaded newer image for hello-world:latest
181 
+				Hello from Docker.
182 
+				This message shows that your installation appears to be working correctly.
17 183
18 
-Currently the Fedora project will only support Docker when running on kernels
19 
-shipped by the distribution. There are kernel changes which will cause issues
20 
-if one decides to step outside that box and run non-distribution kernel packages.
184 
+				To generate this message, Docker took the following steps:
185 
+				 1. The Docker client contacted the Docker daemon.
186 
+				 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
187 
+						(Assuming it was not already locally available.)
188 
+				 3. The Docker daemon created a new container from that image which runs the
189 
+						executable that produces the output you are currently reading.
190 
+				 4. The Docker daemon streamed that output to the Docker client, which sent it
191 
+						to your terminal.
21 192
22 
-## Fedora 21 and later
193 
+				To try something more ambitious, you can run an Ubuntu container with:
194 
+				 $ docker run -it ubuntu bash
23 195
24 
-### Installation
196 
+				For more examples and ideas, visit:
197 
+				 http://docs.docker.com/userguide/
198 
+
199 
+## Start the docker daemon at boot
25 200
26 
-Install the Docker package which will install Docker on our host.
201 
+To ensure Docker starts when you boot your system, do the following:
27 202
28 
-    $ sudo yum -y install docker
203 
+    $ sudo chkconfig docker on
29 204
30 
-To update the Docker package:
31 
-
32 
-    $ sudo yum -y update docker
33 
-
34 
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
35 
-
36 
-### Uninstallation
37 
-
38 
-To uninstall the Docker package:
39 
-
40 
-    $ sudo yum -y remove docker
41 
-
42 
-The above command will not remove images, containers, volumes, or user created
43 
-configuration files on your host. If you wish to delete all images, containers,
44 
-and volumes run the following command:
45 
-
46 
-    $ rm -rf /var/lib/docker
47 
-
48 
-You must delete the user created configuration files manually.
49 
-
50 
-## Fedora 20
51 
-
52 
-### Installation
53 
-
54 
-For `Fedora 20`, there is a package name conflict with a system tray application
55 
-and its executable, so the Docker RPM package was called `docker-io`.
56 
-
57 
-To proceed with `docker-io` installation on Fedora 20, please remove the `docker`
58 
-package first.
59 
-
60 
-    $ sudo yum -y remove docker
61 
-    $ sudo yum -y install docker-io
62 
-
63 
-To update the Docker package:
64 
-
65 
-    $ sudo yum -y update docker-io
66 
-
67 
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
68 
-
69 
-### Uninstallation
70 
-
71 
-To uninstall the Docker package:
72 
-
73 
-    $ sudo yum -y remove docker-io
74 
-
75 
-The above command will not remove images, containers, volumes, or user created
76 
-configuration files on your host. If you wish to delete all images, containers,
77 
-and volumes run the following command:
78 
-
79 
-    $ rm -rf /var/lib/docker
80 
-
81 
-You must delete the user created configuration files manually.
82 
-
83 
-## Starting the Docker daemon
84 
-
85 
-Now that it's installed, let's start the Docker daemon.
86 
-
87 
-    $ sudo systemctl start docker
88 
-
89 
-If we want Docker to start at boot, we should also:
90 
-
91 
-    $ sudo systemctl enable docker
205 
+If you need to add an HTTP Proxy, set a different directory or partition for the
206 
+Docker runtime files, or make other customizations, read our Systemd article to
207 
+learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
92 208
93 
-Now let's verify that Docker is working.
94 209
95 
-    $ sudo docker run -i -t fedora /bin/bash
210 
+## Uninstall
96 211
97 
-> Note: If you get a `Cannot start container` error mentioning SELinux
98 
-> or permission denied, you may need to update the SELinux policies.
99 
-> This can be done using `sudo yum upgrade selinux-policy` and then rebooting.
212 
+You can uninstall the Docker software with `yum`.
100 213
101 
-## Granting rights to users to use Docker
214 
+1. List the package you have installed.
102 215
103 
-The `docker` command line tool contacts the `docker` daemon process via a
104 
-socket file `/var/run/docker.sock` owned by `root:root`. Though it's
105 
-[recommended](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-January/msg00034.html)
106 
-to use `sudo` for docker commands, if users wish to avoid it, an administrator can
107 
-create a `docker` group, have it own `/var/run/docker.sock`, and add users to this group.
216 
+		$ yum list installed | grep docker
217 
+		yum list installed | grep docker
218 
+		docker-engine.x86_64                1.7.0-0.1.fc20
219 
+																																								 @/docker-engine-1.7.0-0.1.fc20.el6.x86_64
108 220
109 
-    $ sudo groupadd docker
110 
-    $ sudo chown root:docker /var/run/docker.sock
111 
-    $ sudo usermod -a -G docker $USERNAME
221 
+2. Remove the package.
112 222
113 
-## Custom daemon options
223 
+		$ sudo yum -y remove docker-engine.x86_64
114 224
115 
-If you need to add an HTTP Proxy, set a different directory or partition for the
116 
-Docker runtime files, or make other customizations, read our Systemd article to
117 
-learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
225 
+	This command does not remove images, containers, volumes, or user-created
226 
+	configuration files on your host.
118 227
119 
-## What next?
228 
+3. To delete all images, containers, and volumes, run the following command:
120 229
121 
-Continue with the [User Guide](/userguide/).
230 
+		$ rm -rf /var/lib/docker
122 231
232 
+4. Locate and delete any user-created configuration files.
docs/installation/rhel.md
History View file @ f9ab04a
... ... 
@@ -12,150 +12,178 @@ parent = "smn_linux"
12 12
13 13 
 Docker is supported on the following versions of RHEL:
14 14
15 
-- [*Red Hat Enterprise Linux 7 (64-bit)*](#red-hat-enterprise-linux-7-installation)
16 
-- [*Red Hat Enterprise Linux 6.6 (64-bit)*](#red-hat-enterprise-linux-66-installation) or later
15 
+- Red Hat Enterprise Linux 7
16 
+- Red Hat Enterprise Linux 6.6 or later
17 
+
18 
+This page instructs you to install using Docker-managed release packages and
19 
+installation mechanisms. Using these packages ensures you get the latest release
20 
+of Docker. If you wish to install using Red Hat-managed packages, consult your
21 
+Red Hat release documentation for information on Red Hat's Docker support.
22 
+
23 
+## Prerequisites
24 
+
25 
+Docker requires a 64-bit installation regardless of your Red Hat version. Docker
26 
+requires that your kernel must be 3.10 at minimum. Red Hat 7 runs the 3.10
27 
+kernel, 6.6 does not. We make an exception for Red Hat 6.6. To run Docker on
28 
+[Red Hat-6.6](http://www.centos.org) or later, you need kernel 2.6.32-431 or
29 
+higher.
30 
+
31 
+To check your current kernel version, open a terminal and use `uname -r` to
32 
+display your kernel version:
33 
+
34 
+    $ uname -r
35 
+    3.10.0-229.el7.x86_64
36 
+
37 
+Finally, is it recommended that you fully update your system. Please keep in
38 
+mind that your system should be fully patched to fix any potential kernel bugs.
39 
+Any reported kernel bugs may have already been fixed on the latest kernel
40 
+packages
41 
+
42 
+
43 
+## Install
44 
+
45 
+You use the same installation procedure for all versions of Red Hat Enterprise,
46 
+only the package you install differs.  There are two packages to choose from:
47 
+
48 
+<table>
49 
+  <tr>
50 
+    <th>Version</th>
51 
+    <th>Package name</th>
52 
+  </tr>
53 
+  <tr>
54 
+    <td>6.6 and  higher</td>
55 
+    <td>
56 
+    <p>
57 
+    <a href="https://get.docker.com/rpm/1.7.0/centos-6/RPMS/x86_64/docker-engine-1.7.0-1.el6.x86_64.rpm">
58 
+    https://get.docker.com/rpm/1.7.0/centos-6/RPMS/x86_64/docker-engine-1.7.0-1.el6.x86_64.rpm</a>
59 
+    <p>
60 
+    <a href="https://get.docker.com/rpm/1.7.0/centos-6/SRPMS/docker-engine-1.7.0-1.el6.src.rpm">
61 
+   https://get.docker.com/rpm/1.7.0/centos-6/SRPMS/docker-engine-1.7.0-1.el6.src.rpm</a>
62 
+    <p>
63 
+    </p>
64 
+    </td>
65 
+  </tr>
66 
+  <tr>
67 
+    <td>7.X</td>
68 
+    <td>
69 
+    <p>
70 
+     <a href="https://get.docker.com/rpm/1.7.0/centos-7/RPMS/x86_64/docker-engine-1.7.0-1.el7.centos.x86_64.rpm">
71 
+    https://get.docker.com/rpm/1.7.0/centos-7/RPMS/x86_64/docker-engine-1.7.0-1.el7.centos.x86_64.rpm</a>
72 
+    </p>
73 
+    <p>
74 
+     <a href="https://get.docker.com/rpm/1.7.0/centos-7/SRPMS/docker-engine-1.7.0-1.el7.centos.src.rpm">
75 
+    https://get.docker.com/rpm/1.7.0/centos-7/SRPMS/docker-engine-1.7.0-1.el7.centos.src.rpm</a>
76 
+    </p>
77 
+    </td>
78 
+  </tr>
79 
+</table>
80 
+
81 
+This procedure depicts an installation on version 6.6.  If you are installing on
82 
+7.X, substitute that package for your installation.
83 
+
84 
+1. Log into your machine as a user with `sudo` or `root` privileges.
85 
+
86 
+2. Download the Docker RPM to the current directory.
87 
+
88 
+		$ curl -O -sSL http://get.docker.com/docker/1.7.0/rpms/centos-6/RPMS/x86_64/docker-engine-1.7.0-0.1.el6.x86_64.rpm
89 
+
90 
+3. Use `yum` to install the package.
91 
+
92 
+		$ sudo yum localinstall --nogpgcheck docker-engine-1.7.0-0.1.el6.x86_64.rpm
93 
+
94 
+5. Start the Docker daemon.
95 
+
96 
+		$ sudo service docker start
97 
+
98 
+6. Verify `docker` is installed correctly.
99 
+
100 
+		$ sudo docker run hello-world
101 
+		Unable to find image 'hello-world:latest' locally
102 
+		latest: Pulling from hello-world
103 
+		a8219747be10: Pull complete
104 
+		91c95931e552: Already exists
105 
+		hello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
106 
+		Digest: sha256:aa03e5d0d5553b4c3473e89c8619cf79df368babd18681cf5daeb82aab55838d
107 
+		Status: Downloaded newer image for hello-world:latest
108 
+		Hello from Docker.
109 
+		This message shows that your installation appears to be working correctly.
110 
+
111 
+		To generate this message, Docker took the following steps:
112 
+		 1. The Docker client contacted the Docker daemon.
113 
+		 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
114 
+				(Assuming it was not already locally available.)
115 
+		 3. The Docker daemon created a new container from that image which runs the
116 
+				executable that produces the output you are currently reading.
117 
+		 4. The Docker daemon streamed that output to the Docker client, which sent it
118 
+				to your terminal.
119 
+
120 
+		To try something more ambitious, you can run an Ubuntu container with:
121 
+		 $ docker run -it ubuntu bash
17 122
18 
-## Kernel support
123 
+		For more examples and ideas, visit:
124 
+		 http://docs.docker.com/userguide/
125 
+
126 
+## Create a docker group
127 
+
128 
+The `docker` daemon binds to a Unix socket instead of a TCP port. By default
129 
+that Unix socket is owned by the user `root` and other users can access it with
130 
+`sudo`. For this reason, `docker` daemon always runs as the `root` user.
131 
+
132 
+To avoid having to use `sudo` when you use the `docker` command, create a Unix
133 
+group called `docker` and add users to it. When the `docker` daemon starts, it
134 
+makes the ownership of the Unix socket read/writable by the `docker` group.
135 
+
136 
+>**Warning**: The `docker` group is equivalent to the `root` user; For details
137 
+>on how this impacts security in your system, see [*Docker Daemon Attack
138 
+>Surface*](/articles/security/#docker-daemon-attack-surface) for details.
139 
+
140 
+To create the `docker` group and add your user:
19 141
20 
-RHEL will only support Docker via the *extras* channel or EPEL package when
21 
-running on kernels shipped by the distribution. There are kernel changes which
22 
-will cause issues if one decides to step outside that box and run
23 
-non-distribution kernel packages.
142 
+1. Log into your machine as a user with `sudo` or `root` privileges.
143 
+
144 
+2. Create the `docker` group and add your user.
145 
+
146 
+    `sudo usermod -aG docker your_username`
147 
+
148 
+3. Log out and log back in.
149 
+
150 
+    This ensures your user is running with the correct permissions.
151 
+
152 
+4. Verify your work by running `docker` without `sudo`.
153 
+
154 
+			$ docker run hello-world
155 
+
156 
+## Start the docker daemon at boot
24 157
25 
-## Red Hat Enterprise Linux 7
158 
+To ensure Docker starts when you boot your system, do the following:
26 159
27 
-### Installation
28 
-
29 
-**Red Hat Enterprise Linux 7 (64 bit)** has [shipped with
30 
-Docker](https://access.redhat.com/site/products/red-hat-enterprise-linux/docker-and-containers).
31 
-An overview and some guidance can be found in the [Release
32 
-Notes](https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.0_Release_Notes/chap-Red_Hat_Enterprise_Linux-7.0_Release_Notes-Linux_Containers_with_Docker_Format.html).
33 
-
34 
-Docker is located in the *extras* channel. To install Docker:
35 
-
36 
-1. Enable the *extras* channel:
37 
-
38 
-        $ sudo subscription-manager repos --enable=rhel-7-server-extras-rpms
39 
-
40 
-2. Install Docker:
41 
-
42 
-        $ sudo yum install docker
43 
-
44 
-Additional installation, configuration, and usage information,
45 
-including a [Get Started with Docker Containers in Red Hat
46 
-Enterprise Linux 7](https://access.redhat.com/site/articles/881893)
47 
-guide, can be found by Red Hat customers on the [Red Hat Customer
48 
-Portal](https://access.redhat.com/).
49 
-
50 
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
51 
-
52 
-### Uninstallation
53 
-
54 
-To uninstall the Docker package:
55 
-
56 
-    $ sudo yum -y remove docker
57 
-
58 
-The above command will not remove images, containers, volumes, or user created
59 
-configuration files on your host. If you wish to delete all images, containers,
60 
-and volumes run the following command:
61 
-
62 
-    $ rm -rf /var/lib/docker
63 
-
64 
-You must delete the user created configuration files manually.
65 
-
66 
-## Red Hat Enterprise Linux 6.6
67 
-
68 
-You will need **64 bit** [RHEL
69 
-6.6](https://access.redhat.com/site/articles/3078#RHEL6) or later, with
70 
-a RHEL 6 kernel version 2.6.32-504.16.2 or higher as this has specific kernel
71 
-fixes to allow Docker to work. Related issues: [#9856](https://github.com/docker/docker/issues/9856).
72 
-
73 
-Docker is available for **RHEL6.6** on EPEL. Please note that
74 
-this package is part of [Extra Packages for Enterprise Linux
75 
-(EPEL)](https://fedoraproject.org/wiki/EPEL), a community effort to
76 
-create and maintain additional packages for the RHEL distribution.
77 
-
78 
-### Kernel support
79 
-
80 
-RHEL will only support Docker via the *extras* channel or EPEL package when
81 
-running on kernels shipped by the distribution. There are things like namespace
82 
-changes which will cause issues if one decides to step outside that box and run
83 
-non-distro kernel packages.
84 
-
85 
-> **Warning**:
86 
-> Please keep your system up to date using `yum update` and rebooting
87 
-> your system. Keeping your system updated ensures critical security
88 
->  vulnerabilities and severe bugs (such as those found in kernel 2.6.32)
89 
-> are fixed.
90 
-
91 
-###  Installation
92 
-
93 
-Firstly, you need to install the EPEL repository. Please follow the
94 
-[EPEL installation
95 
-instructions](https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F).
96 
-
97 
-There is a package name conflict with a system tray application
98 
-and its executable, so the Docker RPM package was called `docker-io`.
99 
-
100 
-To proceed with `docker-io` installation, you may need to remove the
101 
-`docker` package first.
102 
-
103 
-    $ sudo yum -y remove docker
104 
-
105 
-Next, let's install the `docker-io` package which will install Docker on our host.
106 
-
107 
-    $ sudo yum install docker-io
108 
-
109 
-To update the `docker-io` package
110 
-
111 
-    $ sudo yum -y update docker-io
112 
-
113 
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
114 
-
115 
-### Uninstallation
116 
-
117 
-To uninstall the Docker package:
118 
-
119 
-    $ sudo yum -y remove docker-io
120 
-
121 
-The above command will not remove images, containers, volumes, or user created
122 
-configuration files on your host. If you wish to delete all images, containers,
123 
-and volumes run the following command:
124 
-
125 
-    $ rm -rf /var/lib/docker
126 
-
127 
-You must delete the user created configuration files manually.
128 
-
129 
-## Starting the Docker daemon
130 
-
131 
-Now that it's installed, let's start the Docker daemon.
160 
+    $ sudo chkconfig docker on
132 161
133 
-    $ sudo service docker start
162 
+If you need to add an HTTP Proxy, set a different directory or partition for the
163 
+Docker runtime files, or make other customizations, read our Systemd article to
164 
+learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
134 165
135 
-If we want Docker to start at boot, we should also:
136 166
137 
-    $ sudo chkconfig docker on
167 
+## Uninstall
138 168
139 
-Now let's verify that Docker is working.
169 
+You can uninstall the Docker software with `yum`.
140 170
141 
-    $ sudo docker run -i -t fedora /bin/bash
171 
+1. List the package you have installed.
142 172
143 
-> Note: If you get a `Cannot start container` error mentioning SELinux
144 
-> or permission denied, you may need to update the SELinux policies.
145 
-> This can be done using `sudo yum upgrade selinux-policy` and then rebooting.
173 
+		$ yum list installed | grep docker
174 
+		yum list installed | grep docker
175 
+		docker-engine.x86_64                1.7.0-0.1.el6
176 
+																																					 @/docker-engine-1.7.0-0.1.el6.x86_64
146 177
147 
-**Done!**
178 
+2. Remove the package.
148 179
149 
-Continue with the [User Guide](/userguide/).
180 
+		$ sudo yum -y remove docker-engine.x86_64
150 181
151 
-## Custom daemon options
182 
+	This command does not remove images, containers, volumes, or user created
183 
+	configuration files on your host.
152 184
153 
-If you need to add an HTTP Proxy, set a different directory or partition for the
154 
-Docker runtime files, or make other customizations, read our Systemd article to
155 
-learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
185 
+3. To delete all images, containers, and volumes run the following command:
156 186
157 
-## Issues?
187 
+		$ rm -rf /var/lib/docker
158 188
159 
-If you have any issues - please report them directly in the
160 
-[Red Hat Bugzilla for docker-io component](
161 
-https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL&component=docker-io).
189 
+4. Locate and delete any user-created configuration files.
162 190 
\ No newline at end of file