Constraint "${attr.consul.version} semver >= 1.8.0"

Nomad
1
1 Like
2

Hi @aliegrsp,

The error indicates Nomad is not correctly fingerprinting Consul or that it cannot find the Consul API. Do you have any logs available from the Nomad agent?

Thanks,
jrasell and the Nomad team

3

Hey @jrasell ,

I have the same error, but I’m not using Consul. My setup is very simpl/straightforward I know Nomad server IP address beforehand:


cat /etc/nomad.d/nomad.hcl
data_dir = "/var/nomad"
bind_addr = "0.0.0.0"

# Enable the client
client {
  enabled = true
  servers = ["192.168.100.254"]
}

# Disable the server
server {
  enabled = false
}

# Match the datacenter and region of the server
datacenter = "dc1"
region = "global"
4

I have the same error, and I’m not using Consul also.

5

For future, if anyone is having this issue, just add provider to service:

service {
     provider = "nomad"
     ...
}
2 Likes
6

I’m having a very similar issue. I’m trying avoid installing/utilizing consul at this stage of development and running a pure-nomad environment.

Where does this block go? Job definition? Client definition? Server definition?

service {
     provider = "nomad"
     ...
}
7

Hey @will this would go into your job definition:

job "name" {
    group "name" {
        service {
            ...
            provider = "nomad"

thing is, if you’re using consul for service-discovery, this service won’t be discoverable that way IIUC.

I think this service block can also be in the task block if you have it.