User Tools

Site Tools

tools:docker

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tools:docker [2024/08/27 06:25] – Humphrey Boa-Garttools:docker [2024/08/27 07:31] (current) – [Components] Humphrey Boa-Gart
Line 1: Line 1:
 ====== Docker ====== ====== Docker ======
  
-**Docker** is a set of platform as a service (PaaS) products that use OS-level virtualization to deliver software in packages called **containers**. Containers are isolated from one another and bundle their own software, dependencies, libraries and configuration files. Data that is passed to and from the containers is only allowed through well-defined channels. Because all of the containers share the services of a single operating system kernel, they use fewer resources than virtual machines.+**Docker** is a set of platform as a service (PaaS) products that use OS-level virtualization to deliver software in packages called **containers**. Containers are isolated from one another and bundle their own software, dependencies, libraries and configuration files. Data that is passed to and from the containers is only allowed through well-defined channels. Because all of the containers share the services of a single operating system kernel, they use fewer resources than virtual machines. The nature of the virtualization can have many security benefits, when wielded Correctly.
  
-Docker packages are typically distributed as flat inert **images**. These images are used by the Docker engine to generate the aforementioned containers, which is where the package's binaries actually run from. When the container is no longer needed, it can be shut down or destroyed. When the container is needed again, it can be quickly regenerated from the original image. The nature of the virtualization can have many security benefits, when wielded Correctly.+Docker packages are distributed as flat inert **images**. These images are used by the Docker Engine to generate the aforementioned containers, which is where the package's binaries actually run from. When the container is no longer needed, it can be destroyed. When the container is needed again, it can be quickly regenerated from the original image. You can even spawn multiple containers from a single image.
  
-Another summary, from the [[https://docs.docker.com/get-started/docker-overview/|documentation]]:+Another summary, from the [[https://docs.docker.com/get-started/docker-overview/|official documentation]]:
  
 > Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. With Docker, you can manage your infrastructure in the same ways you manage your applications. By taking advantage of Docker's methodologies for shipping, testing, and deploying code, you can significantly reduce the delay between writing code and running it in production. > Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. With Docker, you can manage your infrastructure in the same ways you manage your applications. By taking advantage of Docker's methodologies for shipping, testing, and deploying code, you can significantly reduce the delay between writing code and running it in production.
  
 ===== Components ===== ===== Components =====
 +
 +{{ :tools:dockerlogo.jpg?300|}}
  
 Docker isn't a single piece of software, but rather several components packaged together. We are not going to go in-depth to all the components here, but there are a few basic ones you should have a working knowledge of. Docker isn't a single piece of software, but rather several components packaged together. We are not going to go in-depth to all the components here, but there are a few basic ones you should have a working knowledge of.
Line 15: Line 17:
 First, is the **Docker Engine**, which is the most integral part of the service. It includes: First, is the **Docker Engine**, which is the most integral part of the service. It includes:
  
-  * The **Docker Daemon**, ''dockerd'' which is the service that runs in the background. The daemon handles the deployment of containers. When you first install Docker, you should make sure the daemon is running in [[https://docs.docker.com/engine/security/rootless/|rootless mode]]. +  * The **dockerd** daemon, which is the service that runs in the background. The daemon handles the deployment of containers. When you first install Docker, you should make sure the daemon is running in [[https://docs.docker.com/engine/security/rootless/|rootless mode]] for security purposes. 
-  * APIs which specify interfaces that programs can use to talk to and instruct the Docker daemon.+  * **APIs** which specify interfaces that programs can use to talk to and instruct the Docker daemon.
   * The [[tools:bash|command-line]] interface ''docker'', which is how you will be controlling Docker and your containers.   * The [[tools:bash|command-line]] interface ''docker'', which is how you will be controlling Docker and your containers.
  
-The most basic way to launch containers from images is with the ''docker run'' command. However, you can make things easier by using [[https://docs.docker.com/compose/|Docker Compose]], which launches containers by reading the settings defined in [[https://docs.docker.com/compose/gettingstarted/#step-2-define-services-in-a-compose-file|preconfigured YAML files]].+The most basic way to launch a container from an image is with the ''docker run'' command. This is fine if you are running a single stock container, but quickly becomes cumbersome as you start adding flags and more containers. You can make things easier by using [[https://docs.docker.com/compose/|Docker Compose]], which spawns containers from images by reading the settings defined in [[https://docs.docker.com/compose/gettingstarted/#step-2-define-services-in-a-compose-file|preconfigured YAML files]].
  
-To build your own Docker images, you will be using [[https://docs.docker.com/build/|Docker Build]]. ''docker build'' reads instructions from a special type of config file called [[https://docs.docker.com/build/concepts/dockerfile/|Dockerfiles]] to generate images. These images you can then launch with ''docker run'' or ''docker compose''.+To build your own Docker images, you will be using [[https://docs.docker.com/build/|Docker Build]]. ''docker build'' reads instructions from a special type of config file called a [[https://docs.docker.com/build/concepts/dockerfile/|Dockerfile]] to generate images. You can then spawn containers from these images with ''docker run'' or ''docker compose''.
  
-Finally there is [[https://hub.docker.com/|Docker Hub]], which is the biggest repository of Docker images, though they are oftentimes distributed on other sites as well, such as GitHub.+Finally there is [[https://hub.docker.com/|Docker Hub]], which is the biggest repository of Docker images. They are oftentimes distributed on other sites as well, such as GitHub. **//Be wary what images you choose to download, as many Docker images are not maintained very well, and are riddled with unpatched security exploits!//**
  
 ===== Essential Commands ===== ===== Essential Commands =====
Line 62: Line 64:
   $ docker compose -f /path/to/compose.yaml up -d   $ docker compose -f /path/to/compose.yaml up -d
  
-Restart a container+Restart a container:
  
   $ docker restart CONTAINERNAME   $ docker restart CONTAINERNAME
  
 Stop a container: Stop a container:
 +
 +  $ docker stop CONTAINERNAME
 +
 +Start a stopped container:
 +
 +  $ docker start CONTAINERNAME
 +
 +Kill a container process entirely:
  
   $ docker kill CONTAINERNAME   $ docker kill CONTAINERNAME
Line 74: Line 84:
   $ docker pull IMAGENAME   $ docker pull IMAGENAME
  
-Build a container image from a Dockerfile (Do not specify the Dockerfile itself like you would with the aforementioned ''docker compose'' command and **compose.yaml**! Only the directory the Dockerfile is stored in):+Build a container image from a Dockerfile //(Do not specify the Dockerfile itself like you would with the aforementioned ''docker compose'' command and **compose.yaml**! Only specify the directory the Dockerfile is stored in)//:
  
   $ docker build /path/to/dockerfile/ -t    $ docker build /path/to/dockerfile/ -t 
tools/docker.1724739900.txt.gz · Last modified: 2024/08/27 06:25 by Humphrey Boa-Gart

Find this page online at: https://bestpoint.institute/tools/docker