Nomad Consul connect "dial tcp: lookup unix: Temporary failure in name resolution"
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Nomad v0.11.1 (b43457070037800fcc8442c8ff095ff4005dab33)
I've run into the following problem:
```
May 15 11:18:25 ip-10-1-89-245 nomad[39744]: 2020-05-15T11:18:25.141Z [ERROR] client.alloc_runner.runner_hook: error connecting to grpc: alloc_id=0de4add2-2b81-fed5-7cd6-a05a168e26d6 error="dial tcp: lookup unix: Temporary failure in name resolution" dest=unix:8502
```
Example Consul client config:
```
# Support for Consul Connect
ports {
"grpc" = 8502
}
connect {
enabled = true
}
addresses {
http = "unix:///tmp/consul.sock"
grpc = "unix:///tmp/consul-grpc.sock"
}
```
Example Nomad config:
```
consul {
address = "unix:///tmp/consul.sock"
}
```
From my understanding, to enable GRPC in Consul I must define a port for it.
Does Nomad support GRPC UNIX socket?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing Nomad's Consul Connect gRPC address handling using the provided Consul and Nomad configurations, then reproduce the reported unix-socket resolution error. Done means determining whether gRPC Unix sockets are supported and, if a change is needed, defining the required behavior and validating it against this configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- backend-api-design, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100