{"id":11019,"date":"2022-04-05T06:09:24","date_gmt":"2022-04-05T06:09:24","guid":{"rendered":"https:\/\/blog.cloudthat.com\/?p=11019"},"modified":"2024-06-25T11:03:04","modified_gmt":"2024-06-25T11:03:04","slug":"docker-fundamentals-use-cases-docker-commands","status":"publish","type":"blog","link":"https:\/\/www.cloudthat.com\/resources\/blog\/explore-docker-fundamentals-use-cases-and-docker-commands","title":{"rendered":"Explore Docker Fundamentals, Use Cases, And Docker Commands"},"content":{"rendered":"

The requirement of Docker came into existence to solve application deployment.<\/p>\n

“Hey, it works on your computer but not on mine.”<\/em><\/p>\n

Today we will discuss the fundamentals of Docker. With the help of Docker, deployment of software applications is made easy, thus integrating the DevOps lifecycle for faster release, scalability, and lower downtime. DevOps is a combination of two distinct fields: development and operations. The majority of businesses have taken initiatives to implement DevOps principles. Learn more about the 7 In-demand DevOps skills to nurture an IT Career here. <\/strong><\/a><\/p>\n\n\n\n\n\n\n\n\n\n
\n

TABLE OF CONTENT<\/span><\/strong><\/h2>\n<\/td>\n<\/tr>\n

1. Introduction to Docker<\/a><\/td>\n<\/tr>\n
2. Terms used in Docker<\/a><\/td>\n<\/tr>\n
3. Docker Use Case<\/a><\/td>\n<\/tr>\n
4. Top Docker Commands<\/a><\/td>\n<\/tr>\n
5. Conclusion<\/a><\/td>\n<\/tr>\n
6. About CloudThat <\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

1. Introduction to Docker<\/strong><\/h2>\n

Docker is an open-source tool that helps us automate the deployment process of a software application in virtual machines named containers. Docker’s main benefit is that it enables users to package an application and all of its dependencies into a single unit\u00a0for software development. In addition, unlike virtual machines, containers have low overhead, allowing for more efficient use of the underlying system and resources.<\/p>\n

Learn more about Docker: Lightweight Containers in Limelight here<\/strong><\/a>.<\/p>\n

2. Terms used in Docker<\/strong><\/h3>\n

The following are the more commonly used terms in Docker:<\/p>\n

    \n
  1. Docker Image:<\/strong><\/span><\/li>\n<\/ol>\n

    A Docker image is a read-only blueprint that contains instructions for building a virtual environment to run the application known as\u00a0a Docker container. It gives you a simple way to package applications and pre-configured server environments that you can use privately or share publicly to deploy the application. In simple words, it is like a template used to create a deployment environment.<\/p>\n

      \n
    1. Docker Container:<\/strong><\/span><\/li>\n<\/ol>\n

      Docker Container is an instance of a Docker Image. It creates an isolated environment containing the required software and packages to deploy the application. Docker Containers enable you to package your application and all its dependencies into a container, ensuring that it runs smoothly in any environment.<\/p>\n

        \n
      1. Docker Hub:<\/strong><\/span><\/li>\n<\/ol>\n

        Docker images are stored in a registry, and it can be thought of as a directory of all available Docker images. Users can host their Docker registries and use them to pull pictures if necessary. It works as a central repository to store and track changes in our Images.<\/p>\n

          \n
        1. Docker Daemon: <\/strong><\/span><\/li>\n<\/ol>\n

          The Daemon is a process that runs a background service on the host operating system, which is used to manage the building, running, and distributing of Docker Containers. Docker Clients communicate with the daemon process to run the containers.<\/p>\n

            \n
          1. Docker Client:
            \n<\/strong><\/span>Docker users interact with Docker through the Docker client which has a CLI. When you issue commands like docker run, the client sends them to Daemon, which executes them. The docker command uses the Docker API. The Docker client can communicate with multiple daemons.
            \n<\/strong><\/span><\/li>\n
          2. Docker Registry:\u00a0<\/span><\/strong><\/li>\n<\/ol>\n

            A registry is a storage and content delivery system, holding named Docker images, available in different tagged versions.<\/p>\n

            3. Docker Use Case:<\/strong><\/h2>\n

            Consider a team working on a Java application. Various groups are involved in the Software Development lifecycle: designing, development, testing, production, deployment, etc.<\/p>\n

            The developer will create an environment that includes a Tomcat server. The tester must test the application after it has been developed. The tester will now create a new Tomcat environment to test the application from scratch. The application will be deployed to the production server when the testing is completed. Again, Tomcat must be installed in the production environment to host the Java application. The same Tomcat environment setup is done three times. While various teams are engaged in launching the application,<\/p>\n

            To overcome this problem, we use Docker. In Docker, if we can create an image that contains information about required packages, say Tomcat server, to run the Java application, we can share that image to testing and production environment. Then, they can run that image which creates a container where the Java application gets hosted in an isolated environment.<\/p>\n

            \"Docker<\/a><\/p>\n

            4. Top Docker Commands<\/strong><\/h2>\n

            Hello-World Docker Image<\/h3>\n

            If you are ready with the Docker setup, you can directly try to run the below command to check whether the setup is working correctly.<\/p>\n

            \"Docker<\/a><\/p>\n

            Display existing images:<\/h3>\n

            -><\/strong>To pull an image from Docker Hub use the below command.<\/p>\n

            $ docker pull <image-name><\/pre>\n
            -><\/strong>To display all the images present in our system enter the below command.<\/p>\n
            $ docker images<\/pre>\n
            \"Docker<\/a><\/p>\n
            Run a docker image to start the Container<\/h3>\n
            -><\/strong>To run an image using the below command.<\/p>\n
            $ docker run <image name><\/pre>\n
            Display running Containers<\/h3>\n
            -><\/strong>We can list all the containers which are alive using the below command.<\/p>\n
            $ docker ps<\/pre>\n
            \"Docker<\/a><\/p>\n
            -><\/strong>To get a detailed view of containers that are alive and excited, we can use the below command.<\/p>\n
            $ Docker ps -a<\/pre>\n
            Opening a Container<\/h3>\n
            -><\/strong>To enter into a container and execute commands, we can use the below command.<\/p>\n
            $ docker run -it <imagename> sh\/bash<\/pre>\n
            -><\/strong>You can also use the below command if there is an active container running in Docker. We will get container Id from $ docker ps<\/strong> command.<\/p>\n
            $ docker exec -it <container ID> sh\/bash<\/pre>\n
            \"Docker<\/a><\/p>\n
            Stop a Container<\/h3>\n
            -><\/strong>To stop the container we can use the below command<\/p>\n
            $ docker stop <container ID><\/pre>\n
            Clear all stopped Containers<\/h3>\n
            \"Docker<\/a><\/p>\n
            Deleting an Image<\/h3>\n
            -><\/strong>To delete an image we can use the below command. Image ID can be found in the $ docker images command output.<\/p>\n
            $ docker rmi <image ID><\/pre>\n
            5. Conclusion<\/strong><\/h3>\n
            Customer experiences can make or break a company. In this fast world, software development is advancing at lightning speed, and program managers are coming up with new ideas to develop and deploy software applications easily, and quickly.<\/p>\n
            One of the biggest problems developers usually face is dependency hell, i.e., the application works perfectly fine on the dev\u00a0environment, but when deployed into QA\/production environment, the application throws errors. This is because it does not work, leaving developers with a huge problem to find the cause of the problem and what is missing exactly. Docker eliminates this problem by providing a complete execution guarantee, as everything needed to run the application is already present inside the container, which is an isolated environment and is not dependent on the underlying platform.<\/p>\n
            If you want to learn more about Docker, here is a link to Getting Started with Docker on Azure.<\/strong><\/a><\/p>\n
            6. About CloudThat<\/strong><\/h3>\n
            CloudThat\u00a0<\/strong><\/a>is\u00a0the official Microsoft Gold Partner, AWS Advanced Consulting Partner, and Training partner helping people develop knowledge on cloud and help their businesses aim for higher goals using best in industry cloud computing practices and expertise. We are on a mission to build\u00a0a robust\u00a0cloud computing ecosystem by disseminating\u00a0knowledge on technological intricacies within the cloud space.\u00a0Our blogs, webinars,\u00a0case studies, and white papers\u00a0enable all the stakeholders in the cloud computing sphere.<\/p>\n
            Feel free to drop a comment or any queries regarding React-Redux, cloud adoption, consulting and we will get back to you quickly. To get started, go through\u00a0our\u00a0Expert Advisory\u00a0<\/strong><\/a>page\u00a0and\u00a0Managed Services Package<\/strong><\/a>\u00a0<\/strong>that is\u00a0CloudThat<\/strong><\/a>‘s<\/strong>\u00a0offerings.<\/p>\n
            <\/h3>\n","protected":false},"author":281,"featured_media":11181,"parent":0,"comment_status":"open","ping_status":"open","template":"","blog_category":[3624,3892],"user_email":"pattan.i@cloudthat.com","published_by":"324","primary-authors":"","secondary-authors":"","acf":[],"_links":{"self":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/11019"}],"collection":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog"}],"about":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/types\/blog"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/users\/281"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/comments?post=11019"}],"version-history":[{"count":1,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/11019\/revisions"}],"predecessor-version":[{"id":41162,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/11019\/revisions\/41162"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/"}],"wp:attachment":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/media?parent=11019"}],"wp:term":[{"taxonomy":"blog_category","embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog_category?post=11019"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}