{"id":719,"date":"2023-10-05T11:29:07","date_gmt":"2023-10-05T11:29:07","guid":{"rendered":"https:\/\/blog.vavensoft.com\/?p=719"},"modified":"2023-10-05T11:29:07","modified_gmt":"2023-10-05T11:29:07","slug":"docker-cli","status":"publish","type":"post","link":"https:\/\/blog.vavencloud.com\/?p=719","title":{"rendered":"Exploring Docker Architecture and Command Usage"},"content":{"rendered":"\n

Component of docker architecture<\/h1>\n\n\n\n

Docker uses a client-server architecture, which allows you to interact with Docker through a command-line interface (CLI) or a graphical user interface (GUI) while the Docker daemon (server) does the actual work of managing containers. Here’s an overview of the Docker architecture:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Docker Client<\/strong><\/p>\n\n\n\n

This is the interface that a user interacts with. It’s usually a command-line tool (CLI) or a GUI. When you issue a command like “run a container,” the Docker Client translates it into a request to the Docker Daemon.<\/p>\n\n\n\n

Docker Daemon<\/strong><\/p>\n\n\n\n

The Docker Daemon is a background process running on your system. It’s responsible for the heavy lifting of container management. It listens for API requests from the Docker Client and acts on them. It can create, run, and manage containers, as well as handle tasks like image management, containerizing, data volumes, and network configuration.<\/p>\n\n\n\n

Docker Registry<\/strong><\/p>\n\n\n\n

Docker images, which are important snapshots of applications and their dependencies, are stored in Docker Registries. These are like online repositories where you can upload, share, and download container images. Docker Hub is a popular public registry, but you can also have private ones for your organization.<\/p>\n\n\n\n

Default Registry:<\/strong> Docker comes with a default registry called the Docker Hub. It\u2019s like a public library that contains a vast collection of images for various programming languages and platforms. When you request an image in Docker, it first checks the Docker Hub to see if it\u2019s available there. This is like going to a public library to find a book.<\/p>\n\n\n\n

Private Registry:<\/strong> Just as you can have your personal book collection at home, you can also have your private Docker registry. This is like having your own library where you store images that are specific to your needs, like custom applications or configurations. You can configure<\/p>\n\n\n\n

commands:
to log to the docker hub,<\/p>\n\n\n\n

docker login<\/code><\/pre>\n\n\n\n
Username:\nPassword:<\/pre>\n\n\n\n
Docker Images<\/strong><\/strong><\/h2>\n\n\n\n
Images in Docker serve as templates or snapshots of a file system with a specific set of files and configurations.<\/p>\n\n\n\n
Application Dependencies:<\/strong> Images specify all the libraries, binaries, and resources required for an application to run. This includes everything from the base operating system to any additional software packages or libraries that an application needs to run.<\/p>\n\n\n\n
Launch Processes:<\/strong> Images define the initial command or process that should be executed when a container is started. This command often kicks off the main application or service within the container.<\/p>\n\n\n\n
Commands<\/strong><\/p>\n\n\n\n
To see all the images present in your local machine run<\/p>\n\n\n\n
docker images<\/code><\/pre>\n\n\n\n
To find out images in Docker Hub.<\/p>\n\n\n\n
docker search <image_name><\/code><\/pre>\n\n\n\n
To download\/pull Images from Docker Hub to your local machine.<\/p>\n\n\n\n
docker pull <image_name><\/code><\/pre>\n\n\n\n
To push a Docker image to a registry i.e. Docker Hub<\/p>\n\n\n\n
docker push <image_name>:<tag><\/code><\/pre>\n\n\n\n
To add or change tags for a Docker image<\/p>\n\n\n\n
docker tag <source_image>[:<source_tag>] <target_image>[:<target_tag>]<\/code><\/pre>\n\n\n\n
    \n
  • <source_image>- image id of that image which you want to tag.<\/li>\n\n\n\n
  • :<source_tag>- If the source image has a  tag, you can specify it here. If not leave it default to latest. used when you want to change the tag.<\/li>\n\n\n\n
  • <target_image>This is the new name you want to give to your image <\/li>\n\n\n\n
  • <target_tag>-tag you want to give to your image<\/li>\n<\/ul>\n\n\n\n
    To get detailed information about a Docker image, including its layers and metadata.<\/p>\n\n\n\n
    docker image inspect <image_name\/id>:<tag><\/code><\/pre>\n\n\n\n
    To remove a Docker Image you can use.<\/p>\n\n\n\n
    docker rmi <image_name_or_id><\/code><\/pre>\n\n\n\n
    Docker Build<\/h2>\n\n\n\n
    Docker Build is a core feature of Docker Engine used extensively in software development. At its core, it’s a command that facilitates the creation of Docker images. This process involves taking your application’s source code, along with necessary dependencies and configuration, and packaging it into a standalone, runnable image.<\/p>\n\n\n\n
    Docker begins with a Dockerfile.<\/p>\n\n\n\n
    Docker File<\/h2>\n\n\n\n
    A Dockerfile is like a set of instructions written in plain text. It tells a computer what to do step by step to create a special kind of package called an \u201cimage.\u201d This image can contain everything an application needs to run.<\/p>\n\n\n\n
    So, with a Dockerfile, you can automate the process of building this package. It\u2019s like giving your computer a recipe to follow. It reads the Dockerfile and carries out each instruction to create the image you want. This makes it easier to create and manage these packages for your applications.<\/p>\n\n\n\n
    Here are the most common types of instructions used to build a Docker File,<\/p>\n\n\n\n
    FROM base_image:tag  # A base image use to create the container \n\nMAINTAINER=\"Your Name\"  # author\/owner name \n\nWORKDIR \/app   # Set the working directory inside the container where instruction will be executed\n\nCOPY source_path destination_path   # Copy files from the host into the container\n\nRUN apt-get update && apt-get install -y package1 package2   # Executes a command during the image build process. Commonly used for installing packages and dependencies.\n\nEXPOSE port_number   # Expose ports for the container (for runtime). Informs Docker that the container will listen on the specified port at runtime. It doesn't actually publish the port.\n\nENV VAR_NAME=value   # Sets environment variables inside the container.\n\nCMD [\"executable\", \"arg1\", \"arg2\"]  # It defines the default command to run when a container is started. It can be overridden at runtime.only one CMD per Dockerfile.\n\nVOLUME [\"\/data\"]  # Define a volume for data storage, it helps in creating a mount point and marks it for storing persistent data.\n\nSHELL [\"\/bin\/bash\", \"-c\"]   # Execute a shell command during build..\n\nENTRYPOINT [\"executable\", \"arg1\", \"arg2\"]   # Set the entry point to a script. The ENTRYPOINT instruction specifies the command that should be run when the container starts. It is often used for specifying the main executable or entry point of your application.<\/code><\/pre>\n\n\n\n
    Building images on your local machine<\/strong><\/p>\n\n\n\n
      \n
    • let’s create a docker file to run Hello World<\/li>\n\n\n\n
    •  the first step is to create a docker file in a particular folder named Dockerfie <\/li>\n\n\n\n
    • Edit the docker file and write a code to build an image <\/li>\n<\/ul>\n\n\n\n
      FROM ubuntu\nMAINTAINER <owner_name>\nRUN apt-get update\nCMD [\"echo\",\"Hello World\"]<\/code><\/pre>\n\n\n\n
      build your image from the docker file using the below command <\/p>\n\n\n\n
      #when you are present in tne same directory where dockerfile present \ndocker build <image_name>:<tag> .\n#when you are in different directory yauneed to specify thepath of your dockerfile\ndocker build \/path\/to\/dockerfile\/ <image_name>:<tag> <\/code><\/pre>\n\n\n\n
      Use the docker images<\/strong> command to see the image that you build. you will find your image with the name that you give and a unique Image ID.<\/p>\n\n\n\n
      Containers<\/strong><\/h2>\n\n\n\n
      In Docker, containers are lightweight, self-contained packages for running software. They include everything an application needs, such as code, libraries, and settings. Act as an executable instance of Docker images.<\/p>\n\n\n\n
      Images:<\/strong> Docker images are like blueprints that contain all the instructions for creating a container. They include the application code, dependencies, and configuration.<\/p>\n\n\n\n
      Containers<\/strong>: Containers are the actual running instances of Docker images. When you start a Docker container, you\u2019re essentially using an image to create a live environment to run your application. Each container is isolated from others, so they don\u2019t interfere with each other.<\/p>\n\n\n\n
      Isolation<\/strong>: Docker containers are isolated from each other, much like how objects in code are encapsulated and don\u2019t affect each other\u2019s data.<\/p>\n\n\n\n
      Commands<\/strong><\/p>\n\n\n\n
      To show all the docker processes actively running containers “ps stands for process status”,<\/p>\n\n\n\n
      docker ps<\/code><\/pre>\n\n\n\n
      To see the all containers running in the background<\/p>\n\n\n\n
      docker ps -a<\/code><\/pre>\n\n\n\n
      This command is used to run a container with the help of an image.<\/p>\n\n\n\n
      docker run --name <container_name> <image_id\/name> <\/code><\/pre>\n\n\n\n
      This command is used to view detailed information about a container.<\/p>\n\n\n\n
      docker inspect <container_name\/id><\/code><\/pre>\n\n\n\n
      Start containers from an image 
      –name defines the name of the containers
      -d define container to run in detach mode i.e. running in the background
      -it defines the continuous running of the containers<\/p>\n\n\n\n
      docker run --name <container_name> -it -d <imag_ID\/Name><\/code><\/pre>\n\n\n\n
      Start, Stop, and restart Containers:<\/p>\n\n\n\n
      docker start <container_ID\/Name><\/code><\/pre>\n\n\n\n
      docker stop <container_ID\/Name><\/code><\/pre>\n\n\n\n
      docker restart <container_ID><\/code><\/pre>\n\n\n\n
      Runs a command inside a running container.
      To go inside the container.<\/p>\n\n\n\n
      docker exec -it <container_ID> <command>\ndocker attach <container_ID><\/code><\/pre>\n\n\n\n
      To view details of containers<\/p>\n\n\n\n
      docker inspect <container_ID><\/code><\/pre>\n\n\n\n
      To remove\/delete container.
      -f for forcefully removing the container
      Removes all stopped containers, freeing up disk space<\/p>\n\n\n\n
      docker rm <container_ID>\ndocker container prune<\/code><\/pre>\n\n\n\n
      to display the logs of the container,<\/p>\n\n\n\n
      docker logs <container_ID><\/code><\/pre>\n\n\n\n
      Copies files from your local machine to a container, or vice versa.<\/p>\n\n\n\n
      docker cp <local_path> <container_ID>:<container_path><\/code><\/pre>\n\n\n\n
      To create a volume to store data, volume is basically used to store the data outside the container
      -v used to specify a volume to be mounted to the container <\/p>\n\n\n\n
      docker run -v <volume_name>:<container_path> <image><\/code><\/pre>\n\n\n\n
      Shows real-time resource usage statistics of a container.<\/p>\n\n\n\n
      docker stats <container_ID><\/code><\/pre>\n\n\n\n
      Registries<\/strong><\/h2>\n\n\n\n
      A registry is a library or a storage place for images, which are the building blocks of containers.<\/p>\n\n\n\n
      Default Registry:<\/strong> Docker comes with a default registry called the Docker Hub. It\u2019s like a public library that contains a vast collection of images for various programming languages and platforms. When you request an image in Docker, it first checks the Docker Hub to see if it\u2019s available there. This is like going to a public library to find a book.<\/p>\n\n\n\n
      Private Registry:<\/strong> Just as you can have your personal book collection at home, you can also have your private Docker registry. This is like having your own library where you store images that are specific to your needs, like custom applications or configurations. You can configure<\/p>\n\n\n\n
      Docker engine<\/strong><\/h2>\n\n\n\n
      The Docker Engine is like the heart of Docker, where everything happens. It\u2019s the software that makes containers work on your computer.<\/p>\n\n\n\n
      Docker Daemon:<\/strong> It runs on your computer and does all the heavy lifting. It\u2019s responsible for creating, managing, and running containers.<\/p>\n\n\n\n
      Docker Client<\/strong>: It\u2019s a command-line tool you use to tell the Docker Daemon what to do. You give it special commands, and it communicates with the Daemon to make things happen.<\/p>\n\n\n\n
      Docker compose<\/h2>\n\n\n\n
      Docker Compose is a valuable tool for defining and running multi-container Docker applications. It simplifies the process of configuring and managing complex applications by utilizing a YAML file to specify the setup of your application\u2019s various services. This configuration file acts as a blueprint, and with a single command, you can create and launch all the services according to the defined configuration.<\/p>\n\n\n\n
      The significant benefit of using Docker Compose is that you can specify your application’s entire setup in a single file, which you keep at the root of your project’s repository. This file can be version-controlled, making it easy for others to collaborate on your project. All someone needs to do is clone your repository and start the application using Docker Compose. As a result, you may find many projects on platforms like GitHub and GitLab adopting this approach.<\/p>\n\n\n\n
      command to install docker on Ubuntu <\/p>\n\n\n\n
      sudo apt install docker-compose<\/code><\/pre>\n\n\n\n
      To check the version of the docker <\/p>\n\n\n\n
      docker-compose --version<\/code><\/pre>\n\n\n\n
      Docker-compose.yml File<\/h3>\n\n\n\n
      Docker Compose is the tool we use for setting up our local development environments. To define how the containers work together, Docker Compose relies on a file called docker-compose.yml<\/code>. This file specifies important details, such as which images are needed, which ports should be made available, whether the containers can access the host’s files, and what commands to execute when they begin running. In essence, it’s a blueprint that describes how everything should work together.<\/p>\n\n\n\n
      Running docker-compose <\/p>\n\n\n\n
      docker-compose up -d<\/code><\/pre>\n\n\n\n
      To see running container and their state with ports.<\/p>\n\n\n\n
      docker-compose ps<\/code><\/pre>\n\n\n\n
      To check the logs of the docker-compose use the command: <\/p>\n\n\n\n
      docker-compose logs<\/code><\/pre>\n\n\n\n
      To stop, pause, and  unpause the running  docker-compose: <\/p>\n\n\n\n
      docker-compose stop\ndocker-compose pause\ndocker-compose unpause<\/code><\/pre>\n\n\n\n
      To remove the containers, networks, and volumes associated with this containerized environment, use this\u00a0command:<\/p>\n\n\n\n
      docker-compose down<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"
      Component of docker architecture Docker uses a client-server architecture, which allows you to interact with Docker through a command-line interface (CLI) or a graphical user interface (GUI) while the Docker daemon (server) does the actual work of managing containers. Here’s an overview of the Docker architecture: Docker Client This is the interface that a user […]<\/p>\n","protected":false},"author":1,"featured_media":765,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[],"class_list":["post-719","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-automation-tools"],"_links":{"self":[{"href":"https:\/\/blog.vavencloud.com\/index.php?rest_route=\/wp\/v2\/posts\/719","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.vavencloud.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.vavencloud.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.vavencloud.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.vavencloud.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=719"}],"version-history":[{"count":0,"href":"https:\/\/blog.vavencloud.com\/index.php?rest_route=\/wp\/v2\/posts\/719\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.vavencloud.com\/index.php?rest_route=\/"}],"wp:attachment":[{"href":"https:\/\/blog.vavencloud.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=719"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.vavencloud.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=719"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.vavencloud.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=719"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}