Starting in Docker container: Error initializing core

[heytrav]

I'm attempting to follow the tutorial using a ubuntu:trusty Docker container and am getting the following error when I try to start vault:

root@31a7d422e87f:/# vault server -dev
Error initializing core: failed to lock memory: cannot allocate memory

I'm not sure if this is due to Docker, or if there is something special about memory allocation in general in Docker that needs to be done here so vault will work.

Here is the Dockerfile

[ryanking]

#97

On Thu, Apr 30, 2015 at 4:40 PM, William Travis Holton <
notifications@github.com> wrote:

I'm attempting to follow the tutorial using a ubuntu:trusty Docker
container and am getting the following error when I try to start vault:

root@31a7d422e87f:/# vault server -dev
Error initializing core: failed to lock memory: cannot allocate memory

I'm not sure if this is due to Docker, or if there is something special
about memory allocation in general in Docker that needs to be done here so
vault will work.

Here is the Dockerfile
https://gist.github.com/heytrav/aec594be5af402e13390

—
Reply to this email directly or view it on GitHub
#121.

[heytrav]

Thanks! Closing as a duplicate.

[mitchellh]

@heytrav Its not a bug, you need to give your container the MLOCK cap

[heytrav]

I figured it would be something like that. I just hadn't run across this in Docker before and wasn't sure.

[heytrav]

I added --cap-add IPC_LOCK as in the other #59 and it worked.