bug: mongodb fails to start when using non-default port #526
Description
The reason is that the port is not being used by the probe command (as well as the init command, however due to failing probe it never gets executed anyway)
I've got an implementation of a mongodb services I've been using privately, from which I would like to port missing features (like ability to run a single-member replica set, which is needed to use change streams) to this repo. I can fix this bug while I'm at it.