mirror of https://github.com/docker/cli.git
60c3836365
Previously, `version: "3"` was equivalent to `version: "3.0"`, which caused confusion for many users, as they expected it to be "3.x". docker-compose and docker compose (v2) have adopted the compose-spec (https://compose-spec.io), which no longer has a version field in the compose file, and always picks the "latest" supported version. This changes how `docker stack` interprets "major" version numbers specified in compose-files: When only the major version ("3") is specified, it is now equivalent to "3.x" (latest supported v3 schema). Compose-files that specify both major and minor version (e.g. "3.0" or "3.1") continue to use the existing behavior; validation is down- graded to the specified version and will produce an error if options are used that are not supported in that schema version. This allows users to locally verify that a composse-file does not use options that are not supported in the intended deployment environment (for example if the deploy environment only supports older versions of the schema). Signed-off-by: Sebastiaan van Stijn <github@gone.nl> |
||
|---|---|---|
| .. | ||
| example1.env | ||
| example2.env | ||
| full-example.yml | ||
| full-struct_test.go | ||
| interpolate.go | ||
| loader.go | ||
| loader_test.go | ||
| merge.go | ||
| merge_test.go | ||
| types_test.go | ||
| volume.go | ||
| volume_test.go | ||
| windows_path.go | ||
| windows_path_test.go | ||