-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
error message says need "root" capabilities. Now called "sudo" in vault #4747
Comments
There is a known issue with compatibility between older Vault versions (before Vault 0.10.0) with Nomad 0.8.5. This was corrected and additional testing to prevent regression added in Nomad 0.8.6 via #4698. Is it possible that you are encountering that combination? Or is your concern that the label is incorrect? For the first error, the labels indicate that the token is expected to have update capability or be a root token, so |
A follow-up comment: the I will mark this resolved, but please ping back if this additional information doesn't resolve your concerns. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
not sure, I run the vault server not the nomad server
Operating system and Environment details
linux
Issue
From the nomad error logs.
vault now uses "sudo" not "root" in the capabilities, same effect but different syntax
Reproduction steps
have the wrong permissions on vault paths.
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: