Containerization

Containerization allows you to create self-contained Linux execution environments. Any program and all its dependencies can be bundled up into a single file . Creating a container can be done programmatically, allowing powerful CI and CD pipelines to be formed.
Multiple programs can be added into a single container, but you should limit yourself to one process per container if at all possible. It’s better to have many small containers than one large one. If each container has a tight focus, updates are easier to deploy and issues are easier to diagnose.

Comments

Post a Comment

Popular posts from this blog

CICD pipeline using Jenkins

Image
A typical CI/CD pipeline is linear and one-directional . I t is composed of a few stages, or phases. The first phase  is CI  [   Continuous Integration ] . t akes a commit from   SCM like GIT  and trigger  the build. CI  consist of .  { Checkout , Compile , UNIT TEST , Package} in case of containerized app  docker image creation , docker push  and docker tag also appended. When all these steps are successful, a unique artifact is built, packaged, and published to a repository. This can be a JAR, .tar.gz file, a container image, or whatever is applicable to the chosen language and platform.  CD part has 2 meanings  :-  Continuous Delivery and  Continuous Deployment Continuous Delivery  :-   When and what to promote is a choice. Promotion typically happens when a build is considered to be “good enough”. QA has run their tests, the Product Owner has signed o...
Read more