You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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 enigmaError enabling: Error making API request.URL: POST http://localhost:8200/v1/sys/mounts/enigmaCode: 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.
The text was updated successfully, but these errors were encountered:
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:
Please don't get confused by the "no such file or directory" error, the plugin is there named correctly enigma.1.0.0
I supposed this is related to the fact that Alpine Linux relies on MUSL LIBC instead of the GNU LIBC.
The text was updated successfully, but these errors were encountered: