Add mongoinit to fix initial docker-compose file

[fajfer]

Description

Fix docker compose file based on #1120 (comment)

Contributor Agreement

• I confirm I have signed the Contributor License Agreement

[bean5]

⚠️ Advised: squash

Reason: Merge exists on branch.

[bean5]

I like the idea this gets at. I don't know enough MongoDB (yet) to fully back this. That being said, I didn't see anything that looks obviously dangerous to merge--except if you do not squash it might not as clean of a merge.

[bean5]

Out of scope.

[bean5]

Is this in scope?

[bean5]

Thanks for the contribution @fajfer!

[fajfer]

I like the idea this gets at. I don't know enough MongoDB (yet) to fully back this. That being said, I didn't see anything that looks obviously dangerous to merge--except if you do not squash it might not as clean of a merge.

I kinda forget that I submitted this. I will try to respond today/tomorrow, there's another comment just below the one I submitted that looks more promising as it doesn't require another "init" container. I'm pretty sure it could be strange looking for usual docker users and looks more like a k8s-oriented approach (which imo doesn't fit into compose).

Correct me if I'm wrong @bean5, since I'm so much used to working with Gerrit, but I think GitHub can squash commits while merging the PR? I usually didn't really care about cleanliness of my commit history on GitHub PRs but maybe I should start doing it if it's problematic.