Container image
A container image is the package used to start containers. It includes software and dependencies, but does not automatically include current business data.
A container image is a package containing the files and dependencies needed to start a container. The image is the template; the container started from it runs the processes. To make a change, a built image is replaced with a new image.
In a hypothetical portal project, the team can use the same tested image first in a test environment and then in production. Runtime configuration, access rights and connected databases must still suit each environment.
An image of the portal software is not a backup of orders received in the meantime. Recovery requires backed-up business data and the necessary configuration alongside the appropriate software. Access keys should not be placed unprotected in a distributed image.
Sources
Related terms
- ContainerA container runs application processes in an isolated environment. It can simplify deployment, while backups and operational responsibilities remain necessary.
- BackupA backup is a saved copy used to restore required data or programs later.
- Return-PathReturn-Path records the SMTP reverse path in a header. It explains the technical route for error reports, not a person’s identity.
- Envelope-FromEnvelope-From identifies the SMTP sender for transport and error feedback. It must be distinguished from the visible sender address.
- DMARC aggregate reportA DMARC aggregate report summarises a reporting mail system’s domain checks over a period. It helps examine sending sources and misconfigurations.
- DMARC policyA DMARC policy describes the requested handling of failed domain checks. It repairs neither sending sources nor their alignment.
Articles on this topic
Cloud & Operations with ASES
Hosting, deployment, maintenance and support