MongoDB railway container keeps trashing

Question

We have a very basic setup, and this RANDOMLY broke, see logs:
```MongoDB starting

Memory available to mongo process is less than total system memory

Build Info

Operating System

Options set by command line

Detected unclean shutdown - Lock file is not empty

Storage engine to use detected by data files

Recovering data from the last clean checkpoint.

Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem

Opening WiredTiger

WiredTiger message

WiredTiger opened

WiredTiger recoveryTimestamp

/sys/kernel/mm/transparent_hugepage/enabled is 'always'. We suggest setting it to 'never' in this binary version

vm.max_map_count is too low

Updated wire specification

current featureCompatibilityVersion value

Clearing temp directory

Initializing cluster server parameters from disk

Flow Control is enabled on this deployment

Initializing full-time diagnostic data capture

Setting new configuration state

Timestamp monitor starting

Listening on

Waiting for connections

mongod startup complete

Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost

Writing fatal message

Frame

BACKTRACE

Frame

Frame```

[View Deploy details](https://railway.com/project/dd14bdb3-167b-4cf3-8c35-cf4228ccab35/service/cff1cdb6-8f1d-40b3-a476-73773622fa7f?id=64041505-ceea-4cd2-97e5-3e10f825d04f)

> &#9432; Deployment information is only viewable by project members and Railway employees.