docker-compose up fails when run on a docker version 1.7 up of installed through docker toolbox on win 7 about relay-starter-kit

[chrisbull]

-- SOLUTION --
(Warning: this will remove all your docker settings and data, so use caution, and at own risk)

1. make sure you are using the latest Docker and docker-compose (ya, I know this is obvious)
2. Reset Docker and Remove all data -> Docker -> Preferences -> Reset -> "Remove all data" and "Reset to factory defaults"
3. Re-run docker-compose up - And Voila!

Basically in the initial build of Postgres, if you built the image with another app, it doesn't run the init.db thus does not install the module for uuid-ossp. With the clean reset, it forces Docker to rebuild the Postgres image with the init.db file. (Well at least this is my theory, and why this process worked for me.)

[koistya]

What's your Docker version, 17.06.2-ce?

https://docs.docker.com/docker-for-windows/

[mrtinkz]

Docker version 17.07.0-ce, build 8784753
docker-compose version 1.15.0, build e12f3b94
docker-machine version 0.12.2, build 9371605

[koistya]

Does at least docker-compose build --no-cache work fine? Does you docker-compose work with other projects / docker-compose.yml files?

[mrtinkz]

docker-compose build --no-cache - does not work either. nodejs-api-starter is the only project I am using the docker-compse up

[mrtinkz]

Trying to run on a linux os Fedora Docker version 17.09.0-ce, build afdb6d4

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/

[koistya]

@mrtinkz perhaps your docker-compose tool is outdated.

[mrtinkz]

@koistya I thought about it and updated the docker-compose to the latest, but it's the same result.

[chrisbull]

@mrtinkz: see my solution above. Did you get it working?

[koistya]

You can now launch the API app without a Docker.