-
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
Nomad panic when starting in dev mode with consul and vault on same host #3326
Comments
Hi this is a duplicate of #3324 - we are working on a fix to Consul (-beta2) that should be released tomorrow. |
Here's the Consul beta2 release which fixes this behavior - https://groups.google.com/d/msg/consul-tool/qrdTkFVEBFQ/3hIunM91AAAJ. |
@slackpad Updating to the beta 2 of Consul 1.0 worked. Cheers! |
Thanks for the update! I'll leave this open to see if the Nomad folks want to change that |
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
Operating system and Environment details
Issue
Reproduction steps
I am going on a blitz here and running a consul server agent in dev mode, a vault server in dev mode and attempting to get nomad running in dev mode on my workstation.
I downloaded the nomad 0.6.3 binary as well and got the same result.
Nomad Server logs (if appropriate)
Couldn't find any of note.
Nomad Client logs (if appropriate)
Couldn't find any of note.
Job file (if appropriate)
N/A
Any other questions or items needed, let me know!
Matthew
The text was updated successfully, but these errors were encountered: