FOC - DO1

             Container Technology

Container

  • A container is a generic software package that combines the application's code and all of its dependence to provide a quick and reliable transition between computers environments.
  • Containers offer an infrastructure that makes it possible to launch applications with minimal and immutable packaging. A container image contains the code, runtime, system, tools, system libraries, and setting.

 

Linux Container

  • A group of one or more isolated processes on the Linux operating system is referred to as a container. Because Linux containers are portable and consistent as they move from development to testing to production, all the files required to run them are delivered from a separate image. 
  • Because of this, they operate far more quickly than development pipelines that rely on simulating conventional testing environment.

 

Why Use Linux Container?

  • Consider creating an application. You use a laptop for work, and your surrounding are set up in a particular way. It's possible that other devs have slightly different setups. This setup and particular libraries, dependence, and files are required by the application you are creating.
  • While this is going on, your company has standardized development and production environments, each with its own set of supporting files and parameters. The goal is to as closely replicates those setting locally as you can without incurring the costs associated with rebuilding the server environment.

 

Container V/S Virtualization

  • With virtualization technology, the steamtable package is a virtual computer that comes with both the application and the whole operating system. 
  • The operating system and Kernal are shared by all containers on a server running multiple containerized applications.
  • Each container has its own mount to write to, and the shared operating system components are read-only. Therefore, compared to virtual computers, containers are substantially lighter and consumes significantly fewer resources.

 

Benefits of Container

  • Modernization can be attained by switching to containers. The main purpose of container is guarantee that application is separated from the environment in which they will function.
  • This implies that containerized programs can be installed more quickly and efficiently in practically any setting.
  • Containers frequently have library and software dependencies, which benefits consistency. With this kind of isolation, we can be certain that the finished program will function consistently no matter the setting.
  • The top advantages of containers for business are listed below:
    • Flexibility and output consistency.
    • Infrastructure scalability and optimization.
    • Resilience Portability. 

Docker

  • An open-source program called Docker was created to make and streamline the creation of applications.
  • It is the collection of platform-as-a-service tools for designing, deploying, and testing applications in isolated virtualized environments.
  • Each though the software is rather easy to learn, there are some phrases unique to Docker that new users could find bewildering, understanding terms like volumes, images, containers, and Dockerfiles will take practice and should eventually come naturally. 
  • It is wise to make an effort to understand the fundamental functions of these components. It will hasten the learning process for interacting with them.

 

Terminology

  • Text files called Dockerfiles contain instructions for creating Docker images. It details the base image to use, the programs to install, the setting to utilize, and the instructions to execute in order to produce the desired image.
  • The cloud-based registry service for Docker images is called Docker Hub. Users may store, distribute, and utilise Docker image thanks to it. The largest container registry in the world, Docker Hub, has more the 18 million images and more than 20 billion monthly downloads.
  • A Docker image is a small, standalone, executable file that contains all the components required to run a program, including the code, runtime, system tools, system libraries, and settings. Dockerfiles are used to build Docker images.
  • A runnable instance of Docker image is known as a Docker container. It is a compact, segregated environment that allows other containers to share the operating system kernel. Docker images are used to build Docker containers.
  • A directory or file that is shared between a Docker container and the host computer is referred to as a Docker volume. Data created and utilized by Docker containers is stored on volumes.

 

Comments

Post a Comment

Popular posts from this blog

FOC - E02

Linux Network and Process Management  In Linux, a process is an active program running under a unique Process ID (PID), having its own allocated resources. Processes can be in different states: Running: Actively executing code. Ready: Awaiting CPU time in a queue. Sleeping: Temporarily paused, waiting for an event or process. Stopped: Halted intentionally by user or system. Zombie: Completed but not yet cleaned up.   To manage processes: Use "ps" to view a list of running processes. "ps aux" for a detailed system-wide process list. "ps aux | grep username" to filter by username. View detailed process info with "/proc/PID/status." "top" provides real-time process monitoring. "kill" command stops a process (e.g., "kill <PID>"). For system services, use "systemctl" (e.g., "sudo systemctl status service_
Read more

FOC - E01

LINUX FILE SYSTEM One essential part of the operating system is the Linux file system. It offers a hierarchical data management and organization system. Root Directory: The root directory ("/") is the top-level directory in the Linux file system. Files and subdirectories are found in directories. Data management: Linux file system maintains metadata, sizes, creation dates, and file names. It is responsible for ownership, security, and permissions.   Representation and Organization of Storage Resources: Disk space is allocated for files and directories. It also maintain Directory structure and store Metadata for each file. Pathnames: A pathname is a text string made up of one or more names separated by forward slashes(/) e.g: ./etc/ passwd,/var/log/auth.log, assignment 02 /check, etc. examples of pathnames: ●       /home ●       /etc/passwd ●       usr / wc ●       /var/ ntpstats loopstats Change directory using a relative path:  $pwd /home/kt $cd abc  
Read more