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
Expected Behavior:
a printout of help for the approle authentication similar to 'vault auth help aws' and 'vault auth help github'
Actual Behavior:
INTERNAL ERROR! Found an auth method enabled at approle/, but its type "approle" is not registered in Vault. This is a bug and should be reported. Please open an issue at github.com/hashicorp/vault.
Steps to Reproduce:
Initialize Vault w/in docker w/ the config above. Setup the VAULT_ADDR appropriately. Initialize. Enable the approle auth. Then type the command above to get the error.
Important Factoids:
I am opening port 8200 with -p 8200:8200 w/in my Docker run command
References:
none
The text was updated successfully, but these errors were encountered:
what I ran: docker run -d -v /Users/dalebingham/Projects/vault:/vault --cap-add=IPC_LOCK -p 8200:8200 --rm --name vault --privileged --hostname vault vault server
and then to get a shell into the container: docker exec -it vault /bin/sh
Environment:
Vault Config File:
{
"listener": [{
"tcp": {
"address": "0.0.0.0:8200",
"tls_disable" : 1
}
}],
"storage" :{
"file" : {
"path" : "/vault/data"
}
}
"max_lease_ttl": "10h",
"default_lease_ttl": "10h",
}
Startup Log Output:
none
Expected Behavior:
a printout of help for the approle authentication similar to 'vault auth help aws' and 'vault auth help github'
Actual Behavior:
INTERNAL ERROR! Found an auth method enabled at approle/, but its type "approle" is not registered in Vault. This is a bug and should be reported. Please open an issue at github.com/hashicorp/vault.
Steps to Reproduce:
Initialize Vault w/in docker w/ the config above. Setup the VAULT_ADDR appropriately. Initialize. Enable the approle auth. Then type the command above to get the error.
Important Factoids:
I am opening port 8200 with -p 8200:8200 w/in my Docker run command
References:
none
The text was updated successfully, but these errors were encountered: