strict: warn user about unsupported attributes and reject the compose file.
default: warn user about unsupported attributes, but ignore them.The specification defines the expected configuration syntax and behavior, but - until noted - supporting any of those is OPTIONAL.Ī Compose implementation to parse a Compose file using unsupported attributes SHOULD warn user. Properties in a Compose file, established by the docker-compose tool where the Composeįile format was designed, doesn’t offer any guarantee to the end-user attributes will be actually implemented. The definition of a versioned schema to control the supported Is Platform dependent and can only be confirmed at runtime. We acknowledge that no Compose implementation is expected to support all attributes, and that support for some properties The Compose specification includes properties designed to target a local OCI container runtime,Įxposing Linux kernel specific configuration options, but also some Windows container specific properties, as well as cloud platform features related to resource placement on a cluster, replicated application distribution and scalability. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119. Distribution of this document is unlimited. This document specifies the Compose file format used to define multi-containers applications. The Compose spec merges the legacyĢ.x and 3.x versions, aggregating properties across these formats and is implemented by Compose 1.27.0+. Version of the Compose file format is defined by the Compose Networks, and volumes for a Docker application. The Compose file is a YAML file defining services,
0 kommentar(er)
