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
Omni:~ james$ uname -a
Darwin Omni.local 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64
Issue
Omni:~ james$ nomad -v
Nomad v0.7.0
Omni:~ james$ nomad agent -consul-address=192.168.0.211:8500 -dev 2>&1| head -n 3
flag provided but not defined: -consul-address
==> Usage: nomad agent [options]
Reproduction steps
Replace 192.168.0.211 with the ip address of your primary nic.
Start consul with the following:
sudo consul agent -dev -node consul -advertise 192.168.0.211 -client 192.168.0.211 -dns-port 53
Start nomad with the following
nomad agent -consul-address=192.168.0.211:8500 -dev 2>&1| head -n 3
Note: Running with the following nomad.config does not manifest the same problem
bind_addr="0.0.0.0"# the defaultdata_dir="/Users/james/nomad_data_dir"advertise {
# Defaults to the node's hostname. If the hostname resolves to a loopback# address you must manually configure advertise addresses.http="192.168.0.211"rpc="192.168.0.211"#serf = "192.168.0.211:5648" # non-default ports may be specifiedserf="192.168.0.211"
}
server {
enabled=truebootstrap_expect=1
}
client {
enabled=truenetwork_speed=10options {
"driver.raw_exec.enable" = "1"
}
}
consul {
address="192.168.0.211:8500"
}
The text was updated successfully, but these errors were encountered:
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
Operating system and Environment details
Issue
Reproduction steps
Replace 192.168.0.211 with the ip address of your primary nic.
Note: Running with the following nomad.config does not manifest the same problem
The text was updated successfully, but these errors were encountered: