kelseyhightower / vault-on-google-kubernetes-engine

How to guide on running HashiCorp's Vault on Google Kubernetes Engine

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Error initializing core: Failed to lock memory: cannot allocate memory

dalekurt opened this issue · comments

@sethvargo I an issue with lock memory.

Error initializing core: Failed to lock memory: cannot allocate memory

This usually means that the mlock syscall is not available.
Vault uses mlock to prevent memory from being swapped to
disk. This requires root privileges as well as a machine
that supports mlock. Please enable mlock on your system or
disable Vault from using it. To disable Vault from using it,
set the `disable_mlock` configuration option in your configuration
file.

Do you have any recommendation on resolving this issue without introducing any compromises?