Add config files supporting older versions of docker compose

[alyssadai]

We've encountered a few times now that some institutional servers have (and are likely constrained to) a docker compose version that's a major version below what we are using (i.e., v1.1x.x).

This older (deprecated) compose version both requires different syntax for commands (docker-compose instead of docker compose) and lacks some of the features that compose v2 supports. This means the docker-compose.yml file and other commands need to be adjusted on these systems to be able to successfully deploy a Neurobagel node stack.

Changes that need to be made for docker compose v1:

[alyssadai]

When you have a chance @surchs, could you add the notes from our debugging meeting with Eric today under Changes that need to be made for docker compose v1?

[surchs]

Thanks for the ping @alyssadai. My notes were:

For older versions of docker compose (in this case v1.17.1):

• inline comments in .env files are not ignored (e.g. NB_PORT = 8000 # some comment will not work correctly)
• docker-compose config on these older versions does not seem to create (by default) a dedicated docker network for all the services, which is a problem because we rely on the services being able to discover each other by their names

[github-actions[bot]]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days. We have applied the _flag:stale label to indicate that this issue should be reviewed again. When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this label in the future. Use sparingly!

[github-actions[bot]]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days. We have applied the _flag:stale label to indicate that this issue should be reviewed again. When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this label in the future. Use sparingly!