Author: Konrad

In short, Compose is a tool (now shipped by default with Docker) that allows you to easily define and run multi-container applications using a YAML file. The structure of the YAML file is defined by Compose. The Compose file should be called compose.yaml or compose.yml. Its structure includes the following top-level keys: Digging deeper:The core

Restart policies are rules for restarting containers. There are four:●​ no (default)●​ on-failure●​ always●​ unless-stopped In the table: Y = Restart, N = No Restart How to use it To apply these policies, use --restart <policy> when running a container: or when update:

Docker images are lightweight, read-only packages that contain everything you need to run an application: When a container is running from an image, the container is bound to that image. That means you can’t delete the image while the container is running. It is worth mentioning that an image does not contain a full OS,

The shim (in modern Docker/containerd architecture) is a small process that is started for each container. Its job is to sit between the container runtime and the container process itself. What it does enable is this: So in that sense: Important clarification: So the correct mental model is: But: Summary: The shim does not remove

Good option is to set docker to use this without writing sudo The Ops Perspective check the docker version Download an Image Image is similar to VM templates (for people working in operations) and to classes (for developers). check current (pulled) images Pull the ubuntu:latest image (if you don’t have it) NGINX is a server-side