Version conflicts 0.5 <-> latest

[ChristophSchranz]

Hi,
I had problems in creating a gost stack, where the each version don't conflict.

Months ago, I used for the following version in my docker-compose which worked for me: (and still does on one of my cluster)

geodan/gost-db:0.5
geodan/gost:0.5
geodan/gost-dashboard:0.5

Unfortunalely, this stack results in an error when I recreate it on a new cluster. Opening the Dashboard http://192.168.48.71:8082/#/sensors gives:

{

   "error": {
       "status": "Internal Server Error",
       "code": 500,
       "message": [
           "Error executing query dial tcp 127.0.0.1:5432: getsockopt: connection refused"
       ]
   }

}

The log was (using docker service logs gost_gost-db)
The data directory was initialized by PostgreSQL version 9.6, which is not compatible with this version 10.5.
So it is likely a version issue.

I solved this by using the latest version for each service. However, my problem is that I want to use docker to have a guarantee that the version match each other.
Please give us advices which tagged versions should be used together in order to have a functioning stack.

I'm using:

# uname -a
Linux il071 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
# docker --version
Docker version 18.09.0, build 4d60db4

Best,
Chris

[bertt]

Hi,

In theory we work as follows:

• the docker-compose-0.5.yml (https://github.com/gost/docker-compose/blob/master/docker-compose-0.5.yml) has references to stable versions of components (server, database, dashboard), in this case all 0.5.
• docker-compose.yml (https://github.com/gost/docker-compose/blob/master/docker-compose.yml) has references to (potentially unstable but cutting edge) versions of components (server, database, dashboard), so it always uses the 'latest' tag versions.

If the docker-compose-0.5.yml (https://github.com/gost/docker-compose/blob/master/docker-compose-0.5.yml) doesn't work (anymore) then something has gone wrong, I'll check later this week.