Getting started docker compose file does not work anymore

[pingtimeout]

Describe the bug

In #1367, the getting-started/eclipselink docker-compose file has been split into multiple files. Since then, running the provided docker-compose command fails with the following error:

The following log file is the full output from docker compose -f getting-started/eclipselink/docker-compose-postgres.yml -f getting-started/eclipselink/docker-compose-bootstrap-db.yml -f getting-started/eclipselink/docker-compose.yml up. I am not sure why the trino container emits color codes despite all other service not emitting them but that's beside the point.

docker-compose.log

The dependency between the Postgres service, the Polaris bootstrap service and the Polaris server has been removed and causes this issue. See https://github.com/apache/polaris/pull/1367/files#diff-41a96bcd261e0f563ddf86183d461b9d4d013ec9a3407ee911f4cc0c05f480b4.

To Reproduce

No response

Actual Behavior

No response

Expected Behavior

No response

Additional context

No response

System information

No response

[adnanhemani]

Sorry about that - this was a miss on my part because of the decomposition of the Docker Compose files and on all my tests I did not have an issue with the dependencies loading in the correct order. Guess it was extreme luck that it was working for me. I've created a PR to fix this: #1407

Please let me know if this does not work for you!

[pingtimeout]

Thanks for the quick fix @adnanhemani !