Answer:- The run-list is needed for specifying the Recipes that are needed for running it and the order in which the Recipes will be executed. Some of the advantages of run-list include: • It ensures that the Recipes are running in the same order as specified • The node on which the run-list is to be executed has to be specified • It is transferred from the Workstation to Chef Server and the management console.

Answer:- The starter kit is needed for creating the configuration files in Chef. It gives you the information for interacting with the server and defining the configuration file. You can easily download the starter kit and use it at the desired place on the workstation.

Answer:- Here we give you the steps to follow for updating a Chef Cookbook: From the Workstation run the Knife SSH Run the SSH and Chef-client on the server directly You can use the Chef-client as a daemon for restarting the service as needed.

Answer:- If you want to bootstrap in Chef, then you need the following information: The hostname or Public IP address of the node The user name and password for logging into a particular node Using keys as authentication rather than any login credentials.

Answer:- The Test Kitchen in Chef will help you improve the development lifecycle and enables the Cookbooks on the server. You can also create different virtual machines in cloud or on-premise.

Answer:- We can define Docker as a containerization platform that combines all our applications in a package so that we have all the dependencies to run our applications in any environment. This means, our application will run seamlessly on any environment, and this makes it easy for having a product-ready application. What Docker does is wrap the software needed in a file system that has everything for running the code, providing the runtime and all the necessary libraries and system tools. Containerization technology like Docker will share the same operating system kernel with the machine, and due to this it is extremely fast. This means that we have to run Docker only at the beginning and after that, since our OS is already running, we will have a smooth and seamless process.

Answer:- Containerization is a form of virtualization through which applications are run in containers (isolated user spaces) all using a shared OS. It packs or encapsulates software code and all its dependencies for it to run in a consistent and uniform manner on any infrastructure.

Answer:- Though Docker and Hypervisor might do the same job overall, there are many differences between them in terms of how they work. Docker can be thought of as lightweight since it uses very few resources and also the host kernel rather than creating it like a Hypervisor.

Answer:- Some of the most important and unique features of Docker are as follows: • We can run our Docker container either on our PC or on our enterprise IT system. • Along with the Docker Hub, which is a repository of all containers, we can deploy and download all our applications from a central location. • We can even share our applications with the containers that we create.

Answer:- A Docker image helps in creating Docker containers. We can create the Docker image with the build command; due to this, it creates a container that starts when it begins to run. All the Docker images are stored in the Docker registry such as the public Docker registry. These have minimal amounts of layers within the image so that there is a minimum amount of data on the network.

Answer:- It is a comprehensive set of applications including all its dependencies which share the same OS kernel, along with the other containers running in separate processes within the operating system in a user space. Docker is not tied to any IT infrastructure, and thus it can run on any computer system or on the cloud. We can create a Docker container using Docker images and then run it, or we can use the images that are already created in the Docker Hub. To simplify things, let’s say that the Docker containers are just runtime instances of the Docker image.

Answer:- We can think of Docker Hub as a cloud registry that lets us link the code repositories, create the images, and test them. We can also store our pushed images, or we can link to the Docker Cloud, so that the images can be deployed to the host. We have a centralized container image discovery resource that can be used for the collaboration of our teams, automating the workflow and distribution, and changing management by creating the development pipeline.

Answer:- We can think of a Docker Swarm as the way of orchestrating the Docker containers. We will be able to implement Dockers in a cluster. We can convert our Docker pools into a single Docker Swarm for easy management and monitoring.

Answer:- A Dockerfile is a set of specific instructions that we need to pass on to Docker so that the images can be built. We can think of the Dockerfile as a text document which has all the commands that are needed for creating a Docker image. We can create an automated build that lets us execute multiple command lines one after the other.