Skip to main content

Build your own container


Here I will be using the node container as my base image and will build a new container that will host my custom webhook application

First create a webhook application using node.js on the host machine
  • Install node.js
  • Initiate a project with npm init
npm init should prompt some project related questions.
Install the required dependencies for the project, for our example we need express and body-parser

Update index.js to create a webhook 
Run the project as node index.js
Test that webhook from the browser.

We should get a response back.

Now lets convert this web application into a docker container and execute the same from docker.
To get started, create a file in the same folder where we have created the node project, call it as Dockerfile
Update the contents of the file as below:

FROM node:latest
We are pulling the node image tagged as latest from the docker hub

WORKDIR /app
Create a working directory called app in the container root

COPY . .
This will copy all the contents of the host current directory to /app directory in the container

ENV PORT=1337
This will create an environment variable PORT and set the value to 1337

RUN npm install
This will install all the required dependent node libraries

EXPOSE $PORT
This will expose port 1337 on the container for communication

ENTRY ["node", "index.js"]
This is an array and will have the entry point for the application. Here the container will run "node index.js" to start the application

Build the docker image as docker build -t srinu259/node:latest .

docker build as the name suggest is for building your own images
-t is to tag the image

Example of how tag works:
Here we are building an image with repository srinu259/webhook. This image is tagged with version 1.0


We can verify that the image is successfully downloaded by running docker images

Run the container as docker run -d -p 2337:1337 srinu259/node

-d indicates to run the container in the detached mode
-p is for port mapping. 2337 is the host port mapped to 1337 container port
srinu259/node is our image

Test the webhook from the browser

That's it, the webhook application is now running inside a container!


Labels:

Comments

Post a Comment

Popular posts from this blog

Kubernetes: 15. Multiple Schedulers

Custom Scheduler Kubernetes allows to create custom schedulers There can be multiple schedulers running at a same time apart from the default scheduler or A custom scheduler can replace the default kube-scheduler to become the default one So a few pods that requires additional checks apart from taints and toleration, node affinity can go through the custom scheduler before getting scheduled on the node Whereas the rest of the pods can go through the default kube-scheduler Create Custom Scheduler We can either download the kube-scheduler and run it as a service or alternatively create it using a static pod Below here we are downloading the binaries to run it The property scheduler-name is used to define the name of the scheduler, if not set then it will be defaulted to default-scheduler For your custom schedulers, update this property name to set a custom name for your scheduler For Static pods, the name can be updated directly in the pod-definition file Use kubectl create -f <pod-de...
Post a Comment
Read more

Kubernetes: 19. Configure Application

Configuring application consists of Configuring commands and arguments on applications Configuring environment variables Configuring secrets Docker Commands docker run ubuntu  -> Runs ubuntu container and exit, container CMD is set to [bash], so the container quitely exits docker run ubuntu echo "Hello World" -> Runs ubuntu container, prints "Hello World" exits quitely. To update the default settings, create your own image from the base image lets call this ubuntu-sleeper image FROM ubuntu CMD sleep 5 CMD can also be mentioned in the JSON format like CMD ["sleep", "5"] Note that with JSON format the first element should always be the command to execute,  for eg, it CANNOT be ["sleep 5"] Run build the new ubuntu-sleeper image and run the new image docker build -t ubuntu-sleeper .  -> Build the image docker run ubuntu-sleeper -> Run the new image So the new image will launch ubuntu container, sleep for 5 seconds and quitely ex...
Post a Comment
Read more

Kubernetes: 8. Labels & Selectors

Labels Labels are a way of grouping the objects While Kubernetes understands the objects it create, it is easier to identify the objects by using custom labels With labels you group the objects by types (Pods, Services, ReplicaSet etc) or by Applications For a pod, labels are defined under the metadata section Selectors Selectors are used to filter the objects using labels defined on them Using kubectl and selector pods can be listed by filtering on the labels attached to them If a Selector has multiple labels, they are understood as logical AND, which means pods must match all labels. pod-definition.yaml apiVersion: v1 kind: Pod metadata:      name: myapp-pod      labels:           app: myapp           location: IN spec:      containers:      - name: nginx-container        image: nginx kubectl get pods ...
Post a Comment
Read more