When possible, it’s best to grab “official” images, since they are guaranteed by the Docker team to follow Docker best practices. Most popular open source projects have a corresponding image uploaded to the Docker Registry, which you can use to deploy the software. Most Docker images are distributed via the Docker Hub, which is maintained by the Docker team.
These images use the kernel of the host system, but since they are running inside a Docker container and only see their own file system, it’s perfectly possible to run a distribution like CentOS on an Ubuntu host (or vice-versa). Usually a minimal installation contains only the bare minimum of packages needed to run the image. You can think of a Docker image as a complete Linux installation. Docker ImagesĮach Docker container is a local instance of a Docker image. If you’re already familiar with Docker concepts like volumes, links, and port forwarding then you might want to go ahead and skip on to the next section. Using Docker Compose requires a combination of a bunch of different Docker concepts in one, so before we get started let’s take a minute to review the various concepts involved. In this tutorial, you will install the latest version of Docker Compose to help you manage multi-container applications, and will explore the basic commands of the software.
Docker Compose makes it easier for users to orchestrate the processes of Docker containers, including starting up, shutting down, and setting up intra-container linking and volumes. This became so popular that the Docker team decided to make Docker Compose based on the Fig source, which is now deprecated. The Docker community came up with a popular solution called Fig, which allowed you to use a single YAML file to orchestrate all your Docker containers and configurations. For complex applications with a lot of components, orchestrating all the containers to start up and shut down together (not to mention talk to each other) can quickly become unwieldy.
Docker is a great tool for automating the deployment of Linux applications inside software containers, but to really take full advantage of its potential it’s best if each component of your application runs in its own container.
0 kommentar(er)
