From 80f1bdceeb50d29e4e5b6035439eba1a76790e67 Mon Sep 17 00:00:00 2001 From: Maks3w Date: Sat, 7 Apr 2018 18:04:49 +0200 Subject: [PATCH] Extension fields are only supported from 3.4 Use the minimum supported version in the example --- _includes/content/compose-extfields-sub.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_includes/content/compose-extfields-sub.md b/_includes/content/compose-extfields-sub.md index 0508dca7df..b0e717f2a3 100644 --- a/_includes/content/compose-extfields-sub.md +++ b/_includes/content/compose-extfields-sub.md @@ -3,7 +3,7 @@ special fields can be of any format as long as they are located at the root of your Compose file and their name start with the `x-` character sequence. ```none -version: '2.1' +version: '3.4' x-custom: items: - a @@ -29,7 +29,7 @@ logging: You may write your Compose file as follows: ```none -version: '2.1' +version: '3.4' x-logging: &default-logging options: @@ -50,7 +50,7 @@ It is also possible to partially override values in extension fields using the [YAML merge type](http://yaml.org/type/merge.html). For example: ```none -version: '2.1' +version: '3.4' x-volumes: &default-volume driver: foobar-storage