From the last post,we have understood what is container & why do we use containers in general. Just to recap here are some of the key points Containers are an abstraction at the app layer that packages code and dependencies together. Multiple containers can run
Containers has helped development and DevOps teams to increase agility and accelerate application development & delivery. But with these benefits there could be loss of visibility and control for teams deploying and managing them. As you’re aware, Containers bundle applications with a lot of software and
As you can see from the below Google trend graph,there is quite bit of steady increase in adoption towards Microservices architecture pattern since 2014.That’s because, base for Microservices world is Containers. Linux containers has been around since the early 2000s and architected into Linux in 2007.
Docker as we know,is an open platform for developers and sysadmins to build, ship, and run distributed applications, whether on laptops, data center VMs, or the cloud. Today we are going to check how to configure Jenkins to build Docker Images based on a Dockerfile.
Before we start,little bit of intro on Containers, its an abstraction at the app layer that packages code and dependencies together. Multiple containers can run on the same machine and share the OS kernel with other containers, each running as isolated processes in user space. Containers take