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

Azure Active Directory

Azure Active directory (AAD) is a Identity as a Service. This is a smaller subset of Active directory. This is not a replacement to active directory at all. Azure active directory provides the identity services to the mobile apps and web apps in Private cloud. These apps may be connected to on-premise applications. So an SSO is enabled for these apps. So Azure active directory has very simple functionality. Create Users, Groups. Map groups to network security groups and provide the authentication to the resources. When you login to Azure portal, right upper corner of the screen has username along with the domain. Domain or tenant or organization are used interchangeably. Management of Users and Groups: Cloud identity (create users manually)  Directory synchronized identifiers (users are synchronized)  Add users Adding a cloud identity users makes the user as Guest When you do directory synchronization on Premise AD Groups are synched up wi...
Post a Comment
Read more

Kubernetes: 18. Rollout and Rollback

Deployment When a deployment is created, it triggers a rollout Rollout creates a new revision (version) In the future when new deployment is created,  a new rollout is created The new rollout creates one more "new" version These versions help to keep track of the changes and rollback if necessary Deployment Strategy First strategy is delete and recreate strategy.  Delete all the existing pods and deploy the new updated pods But this comes with application downtime Second strategy and default strategy is Rolling update strategy Kubernetes deletes one pod at a time in the older version and in its place creates a one pod at a time in the newer version Update Strategy Updates can be many things like updating the labels, docker image, replicas etc These are directly updated into the deployment file and the changes are applied When the changes are applied using kubectl apply command, a new rollout and a new revision is created Another way to update the image name is to use the kube...
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