Unsupported version in docker-compose.yml

[Defozo]

I'm trying to run script included in here:
https://github.com/pelias/docker#generic-build-workflow

+ pelias compose pull
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/

docker-compose --version
docker-compose version 1.8.0, build unknown

[missinglink]

You should be safe to change the version number at the top of the docker-compose.yml from 3 to 2.

I'll investigate changing that in the repo.

Otherwise you can upgrade your docker-compose command to a version that supports configs written for version 3.

[afeld]

Yeah,

Compose file format 3.0 was first introduced in Compose release 1.10.0

https://docs.docker.com/compose/compose-file/#compose-and-docker-compatibility-matrix

[orangejulius]

oh hey Aidan! 👋

Let us know if lowering the version worked. I think adoption of newer versions of docker compose hasn't really happened yet, and we aren't using it for anything. Maybe we should go back down.

[sophia-xll]

@Defozo Hello,Defozo. How did you solve this problem? I have the same questions, too.
Did you just change verison of docker-compose.yml from 3 to 2?
Or upgrade your docker-compose command ?
Or upgrade docker ?

[missinglink]

See https://docs.docker.com/compose/compose-file/compose-versioning/ for more information

[missinglink]

I'm going to close this issue, we don't plan to support legacy versions of docker-compose, the costs are simply too high for an open-source project to maintain, plus we would lose out on all the new features.

The original issue related to docker-compose 1.8.0 which was released 27 Jul 2016.
Version 3 of the YAML spec has been supported since 1.13.0+, since release 2 May 2017.

At the time of writing it is 1 March 2019, please upgrade your versions of Docker and docker-compose and try again.