How can we use docker and extend to our build environment ? What is the benefit of doing so ? This article discusses on the use of docker to create images for our build environment and what is the other use case from the build and release point of view.
The sections which we will discuss here are:
Docker is an open platform for developers and sysadmins to build, ship, and run distributed applications. In simpler terms, to package an application as a self contained box that includes everything needed to run the application Benefits of docker include that they are smaller than VMs and have an improved performance. Applications are secure and isolated from other activites of the host system and can effortlessly be deployed and run in multiple environments.
A few of the docker terms are necessary to be understood to enter the build arena for any product:
How to use a docker container:
Used docker to build Symantec product on rhel6 image on a host which is rhel7.That is the beauty of using docker. The hostmachine can be of any OS and can be used to run/build applications of a different OS.
what is inside the <image> ?
If we would like a build that uses various kernel configurations, then there are 2 ways to do so:
Generally when an escalation is recieved, the support engineer or the escalation engineer working on the case needs to search out the sanpshot, kernels used, configurations, dependencies and any other needed information about the release. Why not store the entire GA build area into a docker image ? By doing so, the build environment is readily available for the engineer to use with all the needed dependencies.
Some benefits pointed out:
whereas using docker:
Limitations of using docker as of now is that we cannot use it on rhel5 or any non-linux platform.
The only 2 things that anybody needs to start a build:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.