DOCKER TAG SOFTWARE
DOCKER TAG CODE
DOCKER TAG ZIP

K8s.deployment: Base64 YAML for Kubernetes deployment using this image Healthz: The HTTP endpoint for doing healthchecksĭn: A Docker command example for running from this image

DOCKER TAG SOFTWARE

Releasenotes: Release notes for the packaged software Some possible ideas (all of which could be prefixed with something like “ .”):Ĭi-build: URL to the CI project run that produced the image Since they are simply key-value pairs, your project/organization can specify pretty much anything they desire. Version: Version of the packaged software Revision: Source control revision identifier for the packaged softwareīase.digest: Digest (hash) of the image this image is based onīase.name: Image reference of the image this image is based on

DOCKER TAG CODE

Source: URL to get source code for building the image Image creation/origin metadata is so commonly used that the OCI team publishes a standardized set of keys, all prefixed with “ .”, including: Docker label / OCI image annotation metadata types Standardized labels One of the most common use cases is to document information about the construction of the image which can be used as information in the software supply chain of the image artifact. There are many reasons to use labels for your images such as documenting versioning, including contact info about the project maintainers, or even runtime usage information. Why you should use container image labels Most of these items are well known and used in every Dockerfile, but since label metadata is not something required to run your containers, it is often overlooked. LABEL: Key/value pairs that are not used by the runtime engine USER: Which user to run the process underĮNV: Variable (and its value) to be set in the processes environmentĪRG: Build argument passed into the container build container and used like an environment variable in the scope of the buildĬMD: Command and/or parameters to use to start the process (ENTRYPOINT is similar) If you list the “history” of an image, you will often see zero-byte sized layers because they don’t contain filesystem changes, but rather, metadata to be used at runtime that are commonly added by Dockerfile commands: RPM, APT, NPM, and most other packaging tools have similar metadata stored in them that is used by the tools in the process of installing or running the contained software or for utility purposes by repositories or runtime monitoring systems.Ĭontainer images have metadata stored in their layers too. jar. (FYI “POM” stands for Maven’s Project Object Model) jar built by the popular Maven build tool, there will usually be (among other things) a maven directory that has content such as the effective Maven pom.xml and pom.properties used to build the. are recognized and interpreted by the Java 2 Platform to configure applications, extensions, class loaders, and services”. If we open up a.

DOCKER TAG ZIP

zip archives, they all have a top-level META-INF directory that contains several files and directories that, per the Java 2 Platform spec, “. If you’ve built any kind of software package before, you know that - for the most part - their models include the software, configuration, and sometimes functional data as well as metadata about the package itself.įor example, while Java. Book a live demo Docker / OCI image metadata explained

Docker tag