Enabled mlock

Hi everyone, I'm currently creating a template for the hashicorp vault service (https://developer.hashicorp.com/vault) Here is the source code of the template : https://github.com/EzeXchange-API/vault-railway-template But I got the following error (see the image) The problem is that mlock is not enabled when the container run. It can be enabled very easier by add the flag docker run --cap-add=IPC_LOCK when running docker container. In the documentation, I've see that I can disable the mlock usage (https://developer.hashicorp.com/vault/docs/configuration#disable_mlock) but even if I use the consensus protocol so I need to run 5 containers connected to each others on 5 differents servers... I've seen that I can overidde start commands (https://docs.railway.app/deploy/deployments#start-command) but it only override the entrypoint parameter It's a pain point for me because I need this service for my project. And I don't really want to switch to another cloud service because railway is very simple to use. Do you think Railway will plan or have something in it's roadmap to being able configure this kind of feature provided by docker ? Have a good day

Vault | HashiCorp Developer

Vault | HashiCorp Developer

Explore Vault product documentation, tutorials, and examples.

GitHub

GitHub - EzeXchange-API/vault-railway-template

Contribute to EzeXchange-API/vault-railway-template development by creating an account on GitHub.

Server Configuration | Vault | HashiCorp Developer

Server Configuration | Vault | HashiCorp Developer

Vault server configuration reference.

Railway Docs

Deployments | Railway Docs

Documentation for Railway