I'm experiencing an issue with deploying a MongoDB service. The container consistently fails to start with the following error message:

=========================
Mar 18 19:45:59
Container failed to start
Mar 18 19:45:59
=========================
Mar 18 19:45:59
Mar 18 19:45:59
This image does not have a "7" tag.
Mar 18 19:45:59

What I've tried so far:

1. Used more specific tags like "7.0", "7.0.5" instead of just "7"

2. Tried using the "latest" tag

3. Verified on Docker Hub that these tags do exist for MongoDB

4. Recreated the service multiple times

5. Checked all environment variables to ensure proper configuration

Despite these attempts, the container still fails to start with similar error messages about the image tags not existing.

This seems to be an issue with Railway's ability to recognize or access valid MongoDB image tags.

Has anyone else encountered this issue or know of a workaround? Any assistance would be greatly appreciated.

Thank you!