Quick-start script fails if run a second time (with different data) without bringing containers down first

[maxalbert]

To reproduce:

The first run of the quick-start script succeeds.

$ wget https://raw.githubusercontent.com/Flowminder/FlowKit/master/quick_start.sh

$ bash quick_start.sh
Starting containers (this may take a few minutes)
Pulling flowdb                   ... done
Pulling flowdb_testdata          ... done
Pulling flowdb_synthetic_data    ... done
Pulling worked_examples          ... done
Pulling flowapi                  ... done
Pulling flowauth                 ... done
Pulling flowmachine_query_locker ... done
Pulling flowmachine              ... done
Pulling flowetl                  ... done
Pulling flowetl_db               ... done
[...]
All containers ready!
[...]

However, the second run fails if we try to bring up the system with larger_data but without running bash quick_start.sh stop first.

$ bash quick_start.sh larger_data
Starting containers (this may take a few minutes)
Existing containers are running and will be replaced. Are you sure? [y/N]? y

[...]
flowmachine_query_locker is up-to-date
Creating flowdb_synthetic_data ... 
flowauth is up-to-date
flowapi is up-to-date
Creating flowdb_synthetic_data ... error

ERROR: for flowdb_synthetic_data  Cannot start service flowdb_synthetic_data: driver failed programming external connectivity on endpoint flowdb_synthetic_data (174f969ed534104329099edb017829020356c81f62511bdfd6346185bf59300a): Bind for 0.0.0.0:9000 failed: port is already allocated

ERROR: for flowdb_synthetic_data  Cannot start service flowdb_synthetic_data: driver failed programming external connectivity on endpoint flowdb_synthetic_data (174f969ed534104329099edb017829020356c81f62511bdfd6346185bf59300a): Bind for 0.0.0.0:9000 failed: port is already allocated
ERROR: Encountered errors while bringing up the project.

[greenape]

Guess we need an explicit down in case you aren’t bringing up the same image.

[greenape]

Post #1057, could we resolve this by giving all the containers the same name? Would also reduce the duplication, because compose merges the environment section if overridden in a subsequent docker file.