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:54] – [Docker] Humphrey Boa-Garttools:docker [2024/08/27 07:31] (current) – [Components] Humphrey Boa-Gart
Line 3: Line 3:
 **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** 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 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.+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/|official documentation]]: Another summary, from the [[https://docs.docker.com/get-started/docker-overview/|official documentation]]:
Line 10: Line 10:
  
 ===== 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 19: Line 21:
   * 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. 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 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. 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!//** 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!//**
tools/docker.1724741680.txt.gz · Last modified: 2024/08/27 06:54 by Humphrey Boa-Gart

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