Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The plugin does not work if Vault is running on a container, based on official HashiCorp image hashicorp/vault:1.12.1 (which is derived by Alpine Linux) #6

Closed
denismaggior8 opened this issue Feb 21, 2023 · 0 comments

Comments

@denismaggior8
Copy link
Contributor

After having copied the plugin on the Vault's plugin directory and having registered it (everything worked so far), when you enable the secret engine an error occurs:

$ vault secrets enable enigma

Error enabling: Error making API request.

URL: POST http://localhost:8200/v1/sys/mounts/enigma
Code: 400. Errors:

* invalid backend version: 2 errors occurred:
        * fork/exec /usr/local/libexec/vault/enigma.1.0.0: no such file or directory
        * fork/exec /usr/local/libexec/vault/enigma.1.0.0: no such file or directory

Please don't get confused by the "no such file or directory" error, the plugin is there named correctly enigma.1.0.0

$ kubectl exec -ti vault-0 -n vault -- ls -l /usr/local/libexec/vault/enigma.1.0.0
-rwxr-xr-x    1 vault    vault     15803651 Feb 21 08:51 /usr/local/libexec/vault/enigma.1.0.0

I supposed this is related to the fact that Alpine Linux relies on MUSL LIBC instead of the GNU LIBC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants