As part of my research into Percona’s new Open Source offering, their Percona Monitoring and Management platform, I realized that a core component is provided via a Docker container. Now I’ve previously played around with docker on a small scale, but this needed to be done on an actual server environment on the corporate network. There was one little item that caused a brief moment of grief with the proxy, but I eventually sorted it out.
Docker Engine installation on CentOS7
0. Login as root
1. Update machine
2. Add the Docker yum repo
tee /etc/yum.repos.d/docker.repo <<-‘EOF’[dockerrepo]name=Docker Repositorybaseurl=https://yum.dockerproject.org/repo/main/centos/7/enabled=1gpgcheck=1gpgkey=https://yum.dockerproject.org/gpgEOF
3. Install the Docker Engine Package
yum install docker-engine
4. Start the Daemon
systemctl start docker
5. Set to run at boot
systemctl enable docker
6. Verify Operation with simple test
docker run hello-world
**Note: if you’re behind a proxy, you may notice an error
… dial tcp xx.xx.xx.xx:53: getsockopt: connection refused
You may need to do the following
a. create a systemd drop-in directory for the docker service
b. create a proxy configuration file
…in the directory just created, in my case I needed both an HTTP and an HTTPS proxy to get it to work
Add the following (one line)
Save and exit
c. flush changes
d. Verify that the configuration has been loaded:
systemctl show –property=Environment docker
e. Restart Docker:
systemctl restart docker
Verify Operation with simple test (works, yay!)
docker run hello-world
Unable to find image ‘hello-world:latest’ locally
latest: Pulling from library/hello-world
c04b14da8d14: Pull complete
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.
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
Share images, automate workflows, and more with a free Docker Hub account:
For more examples and ideas, visit: