melvz

Exposing the remote API of a Docker container

Context

In case you find yourself using NodeJS for backend scripting, you can use the power of API calls to manage your Docker containers.

Docker has shell bin commands but it's nice to know the remote API calls so an application can remotely control your containers. This document shows how to setup your docker service (inside Centos 7) to expose the API port.

melvz

yum clean all
rm -Rf /var/cache/yum
yum clean all
yum -y install epel-release
yum -y install git
yum -y install ansible
yum -y --enablerepo=epel install python-pip python-devel python
pip install docker-compose
docker-compose version

melvz

Getting lost in the Jungle

Openshift is designed to be a jungle, with self-contained projects! So for DevOps admins like us, who get knacked on the face by an error code pointing to a Docker containerID, we need to understand how the Docker environment swims inside the World of OpenShift.

Example -- finding a POD based on container log file:

melvz

cricket_paddle

hello1
hello2
hello3

paddle one

melvz

When you need to Scale horizontally...

The following section describes my experiment on how to add a NEW NODE into your existing OpenShift cluster.

Reference:

https://docs.openshift.org/latest/install_config/adding_hosts_to_existing_cluster.html#adding-nodes-advanced

Strategy / plan of attack

melvz

Credits

Credits go to Bryan Sazon (john.bryan.j.sazon@accenture.com) for the original content of his Gist.

I also used reference from https://www.projectatomic.io/blog/2017/05/oo-standalone-registry/

---