Installing Docker on CentOS 7 / RHEL 7 / Fedora 21

ADVERTISEMENT

Installing Docker - Docker Logo
Installing Docker – Docker Logo

Docker is a container virtualization technology that has gained widespread popularity in recent times, it offers more efficient way to deploy the application. With Docker, the applications resides inside the container on top of the Linux operating system. Docker uses Kernel features such as cgroups and namespace to allow independent container to run on single os instance.

In this post, you will learn how to install Docker on CentOS 7 / RHEL 7 / Fedora 21

ADVERTISEMENT
Article will continue after the ad

Note: Docker runs only on 64 bit operating system.

Installing Docker:

Docker is available in standard repository of CentOS, so we don’t have to search for package. For RHEL 7, you must have a valid Redhat subscription to enable Extras rpm’s respository on server. Install it using the following command.

# yum -y install docker

Now you have Docker installed onto your machine, start the Docker service incase if it not started automatically after the installation

# systemctl start docker.service

# systemctl enable docker.service

Troubleshoot:

While starting Docker on CentOS 7, i got a below error.

Apr 18 01:21:00 server docker: /usr/bin/docker: relocation error: /usr/bin/docker: symbol dm_task_get_info_with_deferred_remove, version Base not defined in file libdevmapper.so.1.02 with link time reference

I solved this by installing following packages on CentOS 7.

# yum -y install device-mapper device-mapper-event device-mapper-libs device-mapper-event-libs

Credit: Stackoverflow

Restart Docker service on CentOS 7.

# systemctl restart docker.service

Once the service is started, verify your installation by running the following command.

# docker run -it centos echo Hello-World

Lets see what happens when we run “docker run” command. Docker starts a container with centos base image, since we are running this centos container for first time, the output will look like below.

Unable to find image 'centos:latest' locally
Trying to pull repository docker.io/centos ...
0114405f9ff1: Download complete
511136ea3c5a: Download complete
b6718650e87e: Download complete
3d3c8202a574: Download complete
Status: Downloaded newer image for docker.io/centos:latest
Hello-World

Docker looks for centos image locally, and it is not found, it starts downloading the centos image from docker registry. Once the images has been downloaded, it will start the container and echo the command “Hello-World” in the console which you can see at the end of the output.

Allowing Non-root access:

As you can see in my command, for CentOS i had to run docker as root user. To avoid this you can follow below procedure to allow non-root users to run Docker containers.

Create a group called docker, run the following commands with root privileges.

# groupadd docker

Add a user that is to be a part of docker group, replace “raj” with your own user name.

# useradd raj

Add a user to docker group.

# usermod -aG docker raj

Now you can run a Docker with non-root user.

FirewallD:

FirwallD in CentOS 7 can conflict with Docker, it is recommended to disable the service.

# systemctl stop firewalld.service
# systemctl disable firewalld.servic

When firewalld is started or restarted it will remove the DOCKER chain from iptables, it prevents Docker from working properly.

If you still want to use Systemd, firewalld is must be started before Docker service. In case if you start or restart firewalld after Docker, you will have to restart the Docker daemon.

That’s All!, You can now start working with Docker.

ADVERTISEMENT

POSTS YOU MAY LIKE -:)

Share This Post

  • Santy

    port publish doesnot work in RHEL 7 and CentOS 7
    I have one Apache image when I run with -p 80:80 parameter it publish the port 80 on host system interface and it works perfect but its not working with RHEL 7 and CentOS 7.

    • Giulio

      This is absolutely false. You are probably not considering the firewall

      • Santy

        Your reply is too late 😛
        Well the firewall (default all ACCEPT rules) and selinux were off the time when I had this problem. Also when docker run my image it was adding its own chains in iptable but still it was not functional. May it was an version issue, this problem was there with docker v1.1 in later version it worked perfectly.

        Thanks for your reply BTW 😀

Shares