Merge pull request #13827 from moxiegirl/rpm-rhel-centos-fedora

RPMs update to installation guides

docs/installation/centos.md

@@ -12,153 +12,185 @@ parent = "smn_linux"
 
 Docker is supported on the following versions of CentOS:
 
-- [*CentOS 7 (64-bit)*](#installing-docker-centos-7)
-- [*CentOS 6.5 (64-bit)*](#installing-docker-centos-6.5) or later
+* CentOS 7.X 
+* CentOS 6.5 or higher 
+
+Installation on other binary compatible EL6/EL7 distributions such as Scientific
+Linux might succeed, but Docker does not test or support Docker on these
+distributions.
+
+This page instructs you to install using Docker-managed release packages and
+installation mechanisms. Using these packages ensures you get the latest release
+of Docker. If you wish to install using CentOS-managed packages, consult your
+CentOS documentation.
+
+## Prerequisites
+
+Docker requires a 64-bit installation regardless of your CentOS version. Also,
+your kernel must be 3.10 at minimum. CentOS 7 runs the 3.10 kernel, 6.5 does
+not. We make an exception for CentOS 6.5. To run Docker on
+[CentOS-6.5](https://www.centos.org) or later, you need kernel 2.6.32-431 or
+higher. 
+
+To check your current kernel version, open a terminal and use `uname -r` to
+display your kernel version:
+
+    $ uname -r 
+    2.6.32-431.el6.x86_64
+
+Finally, is it recommended that you fully update your system. Please keep in
+mind that CentOS 6 should be fully patched to fix any potential kernel bugs. Any
+reported kernel bugs may have already been fixed on the latest kernel packages 
+
+## Install
+
+You use the same installation procedure for all versions of CentOS,
+only the package you install differs. There are two packages to choose from:
+
+<table>
+  <tr>
+    <th>Version</th>
+    <th>Package name</th>
+  </tr>
+  <tr>
+    <td>6.5 and  higher</td>
+    <td>
+    <p>
+    <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">
+    https://get.docker.com/rpm/1.7.0/centos-6/RPMS/x86_64/docker-engine-1.7.0-1.el6.x86_64.rpm</a>
+    <p>
+    <a href="https://get.docker.com/rpm/1.7.0/centos-6/SRPMS/docker-engine-1.7.0-1.el6.src.rpm">
+   https://get.docker.com/rpm/1.7.0/centos-6/SRPMS/docker-engine-1.7.0-1.el6.src.rpm</a>
+    <p>
+    </p>
+    </td>
+  </tr>
+  <tr>
+    <td>7.X</td>
+    <td>
+    <p>
+     <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">
+    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>   
+    </p>
+    <p>
+     <a href="https://get.docker.com/rpm/1.7.0/centos-7/SRPMS/docker-engine-1.7.0-1.el7.centos.src.rpm">
+    https://get.docker.com/rpm/1.7.0/centos-7/SRPMS/docker-engine-1.7.0-1.el7.centos.src.rpm</a>   
+    </p>
+    </td>
+  </tr>
+</table>
 
-These instructions are likely work for other binary compatible EL6/EL7 distributions
-such as Scientific Linux, but they haven't been tested.
 
-Please note that due to the current Docker limitations, Docker is able to
-run only on the **64 bit** architecture.
+This procedure depicts an installation on version 6.5. If you are installing on
+7.X, substitute that package for your installation. 
 
-## Kernel support
+1. Log into your machine as a user with `sudo` or `root` privileges.
 
-Currently the CentOS project will only support Docker when running on kernels
-shipped by the distribution. There are kernel changes which will cause issues
-if one decides to step outside that box and run non-distribution kernel packages.
+2. Make sure your existing packages are up-to-date.
 
-To run Docker on [CentOS-6.5](http://www.centos.org) or later, you will need
-kernel version 2.6.32-431 or higher as this has specific kernel fixes to allow
-Docker to run.
+		$ sudo yum update
+		
+3. Download the Docker RPM to the current directory.
+		
+		$ 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
 
-## CentOS-7
+4. Use `yum` to install the package.
 
-### Installation
+		$ sudo yum localinstall --nogpgcheck docker-engine-1.7.0-1.el6.x86_64.rpm
 
-Docker is included by default in the CentOS-Extras repository. To install
-run the following command:
+5. Start the Docker daemon.
 
-    $ sudo yum install docker
+		$ sudo service docker start
 
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
+6. Verify `docker` is installed correctly by running a test image in a container.
 
-### Uninstallation
+		$ sudo docker run hello-world
+		Unable to find image 'hello-world:latest' locally
+		latest: Pulling from hello-world
+		a8219747be10: Pull complete 
+		91c95931e552: Already exists 
+		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.
+		Digest: sha256:aa03e5d0d5553b4c3473e89c8619cf79df368babd1.7.0cf5daeb82aab55838d
+		Status: Downloaded newer image for hello-world:latest
+		Hello from Docker.
+		This message shows that your installation appears to be working correctly.
 
-To uninstall the Docker package:
+		To generate this message, Docker took the following steps:
+		 1. The Docker client contacted the Docker daemon.
+		 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
+				(Assuming it was not already locally available.)
+		 3. The Docker daemon created a new container from that image which runs the
+				executable that produces the output you are currently reading.
+		 4. The Docker daemon streamed that output to the Docker client, which sent it
+				to your terminal.
 
-    $ sudo yum -y remove docker
+		To try something more ambitious, you can run an Ubuntu container with:
+		 $ docker run -it ubuntu bash
+
+		For more examples and ideas, visit:
+		 http://docs.docker.com/userguide/
+ 
+## Create a docker group		
 
-The above command will not remove images, containers, volumes, or user created
-configuration files on your host. If you wish to delete all images, containers,
-and volumes run the following command:
+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 other users can access it with
+`sudo`. For this reason, `docker` daemon always runs as the `root` user.
 
-    $ rm -rf /var/lib/docker
+To avoid having to use `sudo` when you use the `docker` command, create a Unix
+group called `docker` and add users to it. When the `docker` daemon starts, it
+makes the ownership of the Unix socket read/writable by the `docker` group.
 
-You must delete the user created configuration files manually.
+>**Warning**: The `docker` group is equivalent to the `root` user; For details
+>on how this impacts security in your system, see [*Docker Daemon Attack
+>Surface*](/articles/security/#docker-daemon-attack-surface) for details.
 
-## CentOS-6.5
+To create the `docker` group and add your user:
+
+1. Log into Centos as a user with `sudo` privileges.
+
+2. Create the `docker` group and add your user.
+
+    `sudo usermod -aG docker your_username`
 
-### Installation
+3. Log out and log back in.
 
-For CentOS-6.5, the Docker package is part of [Extra Packages
-for Enterprise Linux (EPEL)](https://fedoraproject.org/wiki/EPEL) repository,
-a community effort to create and maintain additional packages for the RHEL distribution.
+    This ensures your user is running with the correct permissions.
 
-Firstly, you need to ensure you have the EPEL repository enabled. Please
-follow the [EPEL installation instructions](
-https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F).
+4. Verify your work by running `docker` without `sudo`.
 
-For CentOS-6, there is a package name conflict with a system tray application
-and its executable, so the Docker RPM package was called `docker-io`.
+		$ docker run hello-world
+ 
+## Start the docker daemon at boot
 
-To proceed with `docker-io` installation on CentOS-6, you may need to remove the
-`docker` package first.
+To ensure Docker starts when you boot your system, do the following:
 
-    $ sudo yum -y remove docker
+      $ sudo chkconfig docker on
 
-Next, let's install the `docker-io` package which will install Docker on our host.
-
-    $ sudo yum install docker-io
-
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
-
-### Uninstallation
-
-To uninstall the Docker package:
-
-    $ sudo yum -y remove docker-io
-
-The above command will not remove images, containers, volumes, or user created
-configuration files on your host. If you wish to delete all images, containers,
-and volumes run the following command:
-
-    $ rm -rf /var/lib/docker
-
-You must delete the user created configuration files manually.
-
-## Manual installation of latest Docker release
-
-While using a package is the recommended way of installing Docker,
-the above package might not be the current release version. If you need the latest
-version, [you can install the binary directly](
-https://docs.docker.com/installation/binaries/).
-
-When installing the binary without a package, you may want
-to integrate Docker with Systemd. For this, install the two unit files
-(service and socket) from [the GitHub
-repository](https://github.com/docker/docker/tree/master/contrib/init/systemd)
-to `/etc/systemd/system`.
-
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
-
-## Starting the Docker daemon
-
-Once Docker is installed, you will need to start the docker daemon.
-
-    $ sudo service docker start
-
-If we want Docker to start at boot, we should also:
-
-    $ sudo chkconfig docker on
-
-Now let's verify that Docker is working. First we'll need to get the latest
-`centos` image.
-
-    $ sudo docker pull centos
-
-Next we'll make sure that we can see the image by running:
-
-    $ sudo docker images centos
+If you need to add an HTTP Proxy, set a different directory or partition for the
+Docker runtime files, or make other customizations, read our Systemd article to
+learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
 
-This should generate some output similar to:
 
-    $ sudo docker images centos
-    REPOSITORY      TAG             IMAGE ID          CREATED             VIRTUAL SIZE
-    centos          latest          0b443ba03958      2 hours ago         297.6 MB
+## Uninstall
 
-Run a simple bash shell to test the image:
+You can uninstall the Docker software with `yum`.  
 
-    $ sudo docker run -i -t centos /bin/bash
+1. List the package you have installed.
 
-If everything is working properly, you'll get a simple bash prompt. Type
-`exit` to continue.
+		$ yum list installed | grep docker
+		yum list installed | grep docker
+		docker-engine.x86_64                1.7.0-1.el6
+																																								 @/docker-engine-1.7.0-1.el6.x86_64.rpm
 
-## Custom daemon options
+2. Remove the package.
 
-If you need to add an HTTP Proxy, set a different directory or partition for the
-Docker runtime files, or make other customizations, read our Systemd article to
-learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
+		$ sudo yum -y remove docker-engine.x86_64 
 
-## Dockerfiles
-The CentOS Project provides a number of sample Dockerfiles which you may use
-either as templates or to familiarize yourself with docker. These templates
-are available on GitHub at [https://github.com/CentOS/CentOS-Dockerfiles](
-https://github.com/CentOS/CentOS-Dockerfiles)
+	This command does not remove images, containers, volumes, or user-created
+	configuration files on your host. 
 
-**Done!** You can either continue with the [Docker User
-Guide](/userguide/) or explore and build on the images yourself.
+3. To delete all images, containers, and volumes, run the following command:
 
-## Issues?
+		$ rm -rf /var/lib/docker
 
-If you have any issues - please report them directly in the
-[CentOS bug tracker](http://bugs.centos.org).
+4. Locate and delete any user-created configuration files.

docs/installation/fedora.md

@@ -12,111 +12,221 @@ parent = "smn_linux"
 
 Docker is supported on the following versions of Fedora:
 
-- [*Fedora 20 (64-bit)*](#fedora-20-installation)
-- [*Fedora 21 and later (64-bit)*](#fedora-21-and-later-installation)
+- Fedora 20 
+- Fedora 21
+- Fedora 22 
+
+This page instructs you to install using Docker-managed release packages and
+installation mechanisms. Using these packages ensures you get the latest release
+of Docker. If you wish to install using Fedora-managed packages, consult your
+Fedora release documentation for information on Fedora's Docker support.
+
+##Prerequisites
+
+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
+version, open a terminal and use `uname -r` to display your kernel version:
+
+    $ uname -r 
+    3.19.5-100.fc20.x86_64
+
+If your kernel is at a older version, you must update it.
+
+Finally, is it recommended that you fully update your system. Please keep in
+mind that your system should be fully patched to fix any potential kernel bugs. Any
+reported kernel bugs may have already been fixed on the latest kernel packages 
+
+
+## Install
+
+You use the same installation procedure for all versions of Fedora,
+only the package you install differs. There are two packages to choose from:
+
+<table>
+  <tr>
+    <th>Version</th>
+    <th>Package name</th>
+  </tr>
+  <tr>
+    <td>Fedora 20</td>
+    <td>
+    <p>
+    <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">
+    https://get.docker.com/rpm/1.7.0/fedora-20/RPMS/x86_64/docker-engine-1.7.0-1.fc20.x86_64.rpm</a>
+        </p>
+    </td>
+        <p>
+    <a href="https://get.docker.com/rpm/1.7.0/fedora-20/SRPMS/docker-engine-1.7.0-1.fc20.src.rpm">
+    https://get.docker.com/rpm/1.7.0/fedora-20/SRPMS/docker-engine-1.7.0-1.fc20.src.rpm/a>
+        </p>
+    </td>
+  </tr>
+  <tr>
+    <td>Fedora 21</td>
+    <td>
+    <p>
+    <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">
+    https://get.docker.com/rpm/1.7.0/fedora-21/RPMS/x86_64/docker-engine-1.7.0-1.fc21.x86_64.rpm</a>
+        </p>
+    </td>
+        <p>
+    <a href="https://get.docker.com/rpm/1.7.0/fedora-21/SRPMS/docker-engine-1.7.0-1.fc21.src.rpm">
+    https://get.docker.com/rpm/1.7.0/fedora-21/SRPMS/docker-engine-1.7.0-1.fc21.src.rpm/a>
+        </p>
+    </td>
+  </tr>
+   <tr>
+    <td>Fedora 22</td>
+    <td>
+    <p>
+    <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">
+    https://get.docker.com/rpm/1.7.0/fedora-22/RPMS/x86_64/docker-engine-1.7.0-1.fc22.x86_64.rpm</a>
+        </p>
+    </td>
+        <p>
+    <a href="https://get.docker.com/rpm/1.7.0/fedora-22/SRPMS/docker-engine-1.7.0-1.fc22.src.rpm">
+    https://get.docker.com/rpm/1.7.0/fedora-22/SRPMS/docker-engine-1.7.0-1.fc22.src.rpm/a>
+        </p>
+    </td>
+  </tr> 
+</table>
+
+
+This procedure depicts an installation on version 21. If you are installing on
+20 or 22, substitute that package for your installation. 
+
+1. Log into your machine as a user with `sudo` or `root` privileges.
+
+2. Make sure you don't have an older version of Docker installed.
+
+		$ yum list installed | grep docker
+	  
+	If you have an older version, remove it using the `yum -y remove <packagename>` command.
+
+3. Download the Docker RPM to the current directory.
+		
+		$ curl -O -sSL https://url_to_package/docker-engine-1.7.0-0.1.fc21.x86_64.rpm
+
+4. Use `yum` to install the package.
+
+		$ sudo yum localinstall --nogpgcheck docker-engine-1.7.0-0.1.fc21.x86_64.rpm
+
+5. Start the Docker daemon.
+
+		$ sudo service docker start
+
+6. Verify `docker` is installed correctly by running a test image in a container.
+
+		$ sudo docker run hello-world
+		Unable to find image 'hello-world:latest' locally
+		latest: Pulling from hello-world
+		a8219747be10: Pull complete 
+		91c95931e552: Already exists 
+		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.
+		Digest: sha256:aa03e5d0d5553b4c3473e89c8619cf79df368babd18681cf5daeb82aab55838d
+		Status: Downloaded newer image for hello-world:latest
+		Hello from Docker.
+		This message shows that your installation appears to be working correctly.
+
+		To generate this message, Docker took the following steps:
+		 1. The Docker client contacted the Docker daemon.
+		 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
+				(Assuming it was not already locally available.)
+		 3. The Docker daemon created a new container from that image which runs the
+				executable that produces the output you are currently reading.
+		 4. The Docker daemon streamed that output to the Docker client, which sent it
+				to your terminal.
+
+		To try something more ambitious, you can run an Ubuntu container with:
+		 $ docker run -it ubuntu bash
+
+		For more examples and ideas, visit:
+		 http://docs.docker.com/userguide/
+ 
+## Create a docker group		
+
+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 other users can access it with
+`sudo`. For this reason, `docker` daemon always runs as the `root` user.
+
+To avoid having to use `sudo` when you use the `docker` command, create a Unix
+group called `docker` and add users to it. When the `docker` daemon starts, it
+makes the ownership of the Unix socket read/writable by the `docker` group.
+
+>**Warning**: The `docker` group is equivalent to the `root` user; For details
+>on how this impacts security in your system, see [*Docker Daemon Attack
+>Surface*](/articles/security/#docker-daemon-attack-surface) for details.
+
+To create the `docker` group and add your user:
+
+1. Log into your system as a user with `sudo` privileges.
+
+2. Create the `docker` group and add your user.
+
+    `sudo usermod -aG docker your_username`
+
+3. Log out and log back in.
+
+    This ensures your user is running with the correct permissions.
+
+4. Verify your work by running `docker` without `sudo`.
+
+        $ docker run hello-world
+				Unable to find image 'hello-world:latest' locally
+				latest: Pulling from hello-world
+				a8219747be10: Pull complete 
+				91c95931e552: Already exists 
+				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.
+				Digest: sha256:aa03e5d0d5553b4c3473e89c8619cf79df368babd18681cf5daeb82aab55838d
+				Status: Downloaded newer image for hello-world:latest
+				Hello from Docker.
+				This message shows that your installation appears to be working correctly.
 
-Currently the Fedora project will only support Docker when running on kernels
-shipped by the distribution. There are kernel changes which will cause issues
-if one decides to step outside that box and run non-distribution kernel packages.
+				To generate this message, Docker took the following steps:
+				 1. The Docker client contacted the Docker daemon.
+				 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
+						(Assuming it was not already locally available.)
+				 3. The Docker daemon created a new container from that image which runs the
+						executable that produces the output you are currently reading.
+				 4. The Docker daemon streamed that output to the Docker client, which sent it
+						to your terminal.
 
-## Fedora 21 and later
+				To try something more ambitious, you can run an Ubuntu container with:
+				 $ docker run -it ubuntu bash
 
-### Installation
+				For more examples and ideas, visit:
+				 http://docs.docker.com/userguide/
+ 
+## Start the docker daemon at boot
 
-Install the Docker package which will install Docker on our host.
+To ensure Docker starts when you boot your system, do the following:
 
-    $ sudo yum -y install docker
+    $ sudo chkconfig docker on
 
-To update the Docker package:
-
-    $ sudo yum -y update docker
-
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
-
-### Uninstallation
-
-To uninstall the Docker package:
-
-    $ sudo yum -y remove docker
-
-The above command will not remove images, containers, volumes, or user created
-configuration files on your host. If you wish to delete all images, containers,
-and volumes run the following command:
-
-    $ rm -rf /var/lib/docker
-
-You must delete the user created configuration files manually.
-
-## Fedora 20
-
-### Installation
-
-For `Fedora 20`, there is a package name conflict with a system tray application
-and its executable, so the Docker RPM package was called `docker-io`.
-
-To proceed with `docker-io` installation on Fedora 20, please remove the `docker`
-package first.
-
-    $ sudo yum -y remove docker
-    $ sudo yum -y install docker-io
-
-To update the Docker package:
-
-    $ sudo yum -y update docker-io
-
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
-
-### Uninstallation
-
-To uninstall the Docker package:
-
-    $ sudo yum -y remove docker-io
-
-The above command will not remove images, containers, volumes, or user created
-configuration files on your host. If you wish to delete all images, containers,
-and volumes run the following command:
-
-    $ rm -rf /var/lib/docker
-
-You must delete the user created configuration files manually.
-
-## Starting the Docker daemon
-
-Now that it's installed, let's start the Docker daemon.
-
-    $ sudo systemctl start docker
-
-If we want Docker to start at boot, we should also:
-
-    $ sudo systemctl enable docker
+If you need to add an HTTP Proxy, set a different directory or partition for the
+Docker runtime files, or make other customizations, read our Systemd article to
+learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
 
-Now let's verify that Docker is working.
 
-    $ sudo docker run -i -t fedora /bin/bash
+## Uninstall
 
-> Note: If you get a `Cannot start container` error mentioning SELinux
-> or permission denied, you may need to update the SELinux policies.
-> This can be done using `sudo yum upgrade selinux-policy` and then rebooting.
+You can uninstall the Docker software with `yum`.  
 
-## Granting rights to users to use Docker
+1. List the package you have installed.
 
-The `docker` command line tool contacts the `docker` daemon process via a
-socket file `/var/run/docker.sock` owned by `root:root`. Though it's
-[recommended](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-January/msg00034.html)
-to use `sudo` for docker commands, if users wish to avoid it, an administrator can
-create a `docker` group, have it own `/var/run/docker.sock`, and add users to this group.
+		$ yum list installed | grep docker
+		yum list installed | grep docker
+		docker-engine.x86_64                1.7.0-0.1.fc20
+																																								 @/docker-engine-1.7.0-0.1.fc20.el6.x86_64
 
-    $ sudo groupadd docker
-    $ sudo chown root:docker /var/run/docker.sock
-    $ sudo usermod -a -G docker $USERNAME
+2. Remove the package.
 
-## Custom daemon options
+		$ sudo yum -y remove docker-engine.x86_64 
 
-If you need to add an HTTP Proxy, set a different directory or partition for the
-Docker runtime files, or make other customizations, read our Systemd article to
-learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
+	This command does not remove images, containers, volumes, or user-created
+	configuration files on your host. 
 
-## What next?
+3. To delete all images, containers, and volumes, run the following command:
 
-Continue with the [User Guide](/userguide/).
+		$ rm -rf /var/lib/docker
 
+4. Locate and delete any user-created configuration files.

docs/installation/rhel.md

@@ -12,150 +12,178 @@ parent = "smn_linux"
 
 Docker is supported on the following versions of RHEL:
 
-- [*Red Hat Enterprise Linux 7 (64-bit)*](#red-hat-enterprise-linux-7-installation)
-- [*Red Hat Enterprise Linux 6.6 (64-bit)*](#red-hat-enterprise-linux-66-installation) or later
+- Red Hat Enterprise Linux 7 
+- Red Hat Enterprise Linux 6.6 or later
+
+This page instructs you to install using Docker-managed release packages and
+installation mechanisms. Using these packages ensures you get the latest release
+of Docker. If you wish to install using Red Hat-managed packages, consult your
+Red Hat release documentation for information on Red Hat's Docker support.
+
+## Prerequisites
+
+Docker requires a 64-bit installation regardless of your Red Hat version. Docker
+requires that your kernel must be 3.10 at minimum. Red Hat 7 runs the 3.10
+kernel, 6.6 does not. We make an exception for Red Hat 6.6. To run Docker on
+[Red Hat-6.6](http://www.centos.org) or later, you need kernel 2.6.32-431 or
+higher. 
+
+To check your current kernel version, open a terminal and use `uname -r` to
+display your kernel version:
+
+    $ uname -r 
+    3.10.0-229.el7.x86_64
+
+Finally, is it recommended that you fully update your system. Please keep in
+mind that your system should be fully patched to fix any potential kernel bugs.
+Any reported kernel bugs may have already been fixed on the latest kernel
+packages 
+
+
+## Install
+
+You use the same installation procedure for all versions of Red Hat Enterprise,
+only the package you install differs.  There are two packages to choose from:
+
+<table>
+  <tr>
+    <th>Version</th>
+    <th>Package name</th>
+  </tr>
+  <tr>
+    <td>6.6 and  higher</td>
+    <td>
+    <p>
+    <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">
+    https://get.docker.com/rpm/1.7.0/centos-6/RPMS/x86_64/docker-engine-1.7.0-1.el6.x86_64.rpm</a>
+    <p>
+    <a href="https://get.docker.com/rpm/1.7.0/centos-6/SRPMS/docker-engine-1.7.0-1.el6.src.rpm">
+   https://get.docker.com/rpm/1.7.0/centos-6/SRPMS/docker-engine-1.7.0-1.el6.src.rpm</a>
+    <p>
+    </p>
+    </td>
+  </tr>
+  <tr>
+    <td>7.X</td>
+    <td>
+    <p>
+     <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">
+    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>   
+    </p>
+    <p>
+     <a href="https://get.docker.com/rpm/1.7.0/centos-7/SRPMS/docker-engine-1.7.0-1.el7.centos.src.rpm">
+    https://get.docker.com/rpm/1.7.0/centos-7/SRPMS/docker-engine-1.7.0-1.el7.centos.src.rpm</a>   
+    </p>
+    </td>
+  </tr>
+</table>
+
+This procedure depicts an installation on version 6.6.  If you are installing on
+7.X, substitute that package for your installation. 
+
+1. Log into your machine as a user with `sudo` or `root` privileges.
+
+2. Download the Docker RPM to the current directory.
+		
+		$ 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
+
+3. Use `yum` to install the package.
+
+		$ sudo yum localinstall --nogpgcheck docker-engine-1.7.0-0.1.el6.x86_64.rpm
+
+5. Start the Docker daemon.
+
+		$ sudo service docker start
+
+6. Verify `docker` is installed correctly.
+
+		$ sudo docker run hello-world
+		Unable to find image 'hello-world:latest' locally
+		latest: Pulling from hello-world
+		a8219747be10: Pull complete 
+		91c95931e552: Already exists 
+		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.
+		Digest: sha256:aa03e5d0d5553b4c3473e89c8619cf79df368babd18681cf5daeb82aab55838d
+		Status: Downloaded newer image for hello-world:latest
+		Hello from Docker.
+		This message shows that your installation appears to be working correctly.
+
+		To generate this message, Docker took the following steps:
+		 1. The Docker client contacted the Docker daemon.
+		 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
+				(Assuming it was not already locally available.)
+		 3. The Docker daemon created a new container from that image which runs the
+				executable that produces the output you are currently reading.
+		 4. The Docker daemon streamed that output to the Docker client, which sent it
+				to your terminal.
+
+		To try something more ambitious, you can run an Ubuntu container with:
+		 $ docker run -it ubuntu bash
 
-## Kernel support
+		For more examples and ideas, visit:
+		 http://docs.docker.com/userguide/
+ 
+## Create a docker group		
+
+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 other users can access it with
+`sudo`. For this reason, `docker` daemon always runs as the `root` user.
+
+To avoid having to use `sudo` when you use the `docker` command, create a Unix
+group called `docker` and add users to it. When the `docker` daemon starts, it
+makes the ownership of the Unix socket read/writable by the `docker` group.
+
+>**Warning**: The `docker` group is equivalent to the `root` user; For details
+>on how this impacts security in your system, see [*Docker Daemon Attack
+>Surface*](/articles/security/#docker-daemon-attack-surface) for details.
+
+To create the `docker` group and add your user:
 
-RHEL will only support Docker via the *extras* channel or EPEL package when
-running on kernels shipped by the distribution. There are kernel changes which
-will cause issues if one decides to step outside that box and run
-non-distribution kernel packages.
+1. Log into your machine as a user with `sudo` or `root` privileges.
+
+2. Create the `docker` group and add your user.
+
+    `sudo usermod -aG docker your_username`
+
+3. Log out and log back in.
+
+    This ensures your user is running with the correct permissions.
+
+4. Verify your work by running `docker` without `sudo`.
+
+			$ docker run hello-world
+ 
+## Start the docker daemon at boot
 
-## Red Hat Enterprise Linux 7
+To ensure Docker starts when you boot your system, do the following:
 
-### Installation
-
-**Red Hat Enterprise Linux 7 (64 bit)** has [shipped with
-Docker](https://access.redhat.com/site/products/red-hat-enterprise-linux/docker-and-containers).
-An overview and some guidance can be found in the [Release
-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).
-
-Docker is located in the *extras* channel. To install Docker:
-
-1. Enable the *extras* channel:
-
-        $ sudo subscription-manager repos --enable=rhel-7-server-extras-rpms
-
-2. Install Docker:
-
-        $ sudo yum install docker 
-
-Additional installation, configuration, and usage information,
-including a [Get Started with Docker Containers in Red Hat
-Enterprise Linux 7](https://access.redhat.com/site/articles/881893)
-guide, can be found by Red Hat customers on the [Red Hat Customer
-Portal](https://access.redhat.com/).
-
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
-
-### Uninstallation
-
-To uninstall the Docker package:
-
-    $ sudo yum -y remove docker
-
-The above command will not remove images, containers, volumes, or user created
-configuration files on your host. If you wish to delete all images, containers,
-and volumes run the following command:
-
-    $ rm -rf /var/lib/docker
-
-You must delete the user created configuration files manually.
-
-## Red Hat Enterprise Linux 6.6
-
-You will need **64 bit** [RHEL
-6.6](https://access.redhat.com/site/articles/3078#RHEL6) or later, with
-a RHEL 6 kernel version 2.6.32-504.16.2 or higher as this has specific kernel
-fixes to allow Docker to work. Related issues: [#9856](https://github.com/docker/docker/issues/9856).
-
-Docker is available for **RHEL6.6** on EPEL. Please note that
-this package is part of [Extra Packages for Enterprise Linux
-(EPEL)](https://fedoraproject.org/wiki/EPEL), a community effort to
-create and maintain additional packages for the RHEL distribution.
-
-### Kernel support
-
-RHEL will only support Docker via the *extras* channel or EPEL package when
-running on kernels shipped by the distribution. There are things like namespace
-changes which will cause issues if one decides to step outside that box and run
-non-distro kernel packages.
-
-> **Warning**:
-> Please keep your system up to date using `yum update` and rebooting
-> your system. Keeping your system updated ensures critical security
->  vulnerabilities and severe bugs (such as those found in kernel 2.6.32)
-> are fixed.
-
-###  Installation
-
-Firstly, you need to install the EPEL repository. Please follow the
-[EPEL installation
-instructions](https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F).
-
-There is a package name conflict with a system tray application
-and its executable, so the Docker RPM package was called `docker-io`.
-
-To proceed with `docker-io` installation, you may need to remove the
-`docker` package first.
-
-    $ sudo yum -y remove docker
-
-Next, let's install the `docker-io` package which will install Docker on our host.
-
-    $ sudo yum install docker-io
-
-To update the `docker-io` package
-
-    $ sudo yum -y update docker-io
-
-Please continue with the [Starting the Docker daemon](#starting-the-docker-daemon).
-
-### Uninstallation
-
-To uninstall the Docker package:
-
-    $ sudo yum -y remove docker-io
-
-The above command will not remove images, containers, volumes, or user created
-configuration files on your host. If you wish to delete all images, containers,
-and volumes run the following command:
-
-    $ rm -rf /var/lib/docker
-
-You must delete the user created configuration files manually.
-
-## Starting the Docker daemon
-
-Now that it's installed, let's start the Docker daemon.
+    $ sudo chkconfig docker on
 
-    $ sudo service docker start
+If you need to add an HTTP Proxy, set a different directory or partition for the
+Docker runtime files, or make other customizations, read our Systemd article to
+learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
 
-If we want Docker to start at boot, we should also:
 
-    $ sudo chkconfig docker on
+## Uninstall
 
-Now let's verify that Docker is working.
+You can uninstall the Docker software with `yum`.  
 
-    $ sudo docker run -i -t fedora /bin/bash
+1. List the package you have installed.
 
-> Note: If you get a `Cannot start container` error mentioning SELinux
-> or permission denied, you may need to update the SELinux policies.
-> This can be done using `sudo yum upgrade selinux-policy` and then rebooting.
+		$ yum list installed | grep docker
+		yum list installed | grep docker
+		docker-engine.x86_64                1.7.0-0.1.el6
+																																					 @/docker-engine-1.7.0-0.1.el6.x86_64
 
-**Done!**
+2. Remove the package.
 
-Continue with the [User Guide](/userguide/).
+		$ sudo yum -y remove docker-engine.x86_64 
 
-## Custom daemon options
+	This command does not remove images, containers, volumes, or user created
+	configuration files on your host. 
 
-If you need to add an HTTP Proxy, set a different directory or partition for the
-Docker runtime files, or make other customizations, read our Systemd article to
-learn how to [customize your Systemd Docker daemon options](/articles/systemd/).
+3. To delete all images, containers, and volumes run the following command:
 
-## Issues?
+		$ rm -rf /var/lib/docker
 
-If you have any issues - please report them directly in the
-[Red Hat Bugzilla for docker-io component](
-https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL&component=docker-io).
+4. Locate and delete any user-created configuration files.