shield (vault embedded) failure with jammy stemcell

shield (vault) doesn't start on jammy stemcell

Observed behavior

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.

Workaround applied

https://support.hashicorp.com/hc/en-us/articles/115012787688-Vault-and-mlock-

Hello,
Do you plan to fix it in the next release ?
Thanks and regards,
Jean-Christophe.

There are plans to get Shield working on the Jammy stemcell.

So release 9.1.2 does not work for you?

Hello,
In our context, release 9.1.2 can't be used because of :

Due to updates to vault for security reasons, this version of shield no longer is able to initialize a new shield deployment, but can still update an existing shield deployment. This will be resolved in a future release, but in the mean time, deploy with the v9.1.0 deployment.
```
Regards,
Jean-Christophe.

Navigation Menu

Repository navigation

shield (vault embedded) failure with jammy stemcell #195

Observed behavior

Workaround applied

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

shield (vault embedded) failure with jammy stemcell #195

Description

Observed behavior

Workaround applied

Activity

JCL38-ORANGE commented on Aug 24, 2023

norman-abramovitz commented on Aug 24, 2023

JCL38-ORANGE commented on Oct 5, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions