Skip to content
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

Support for making Nomad listen on Unix Domain Socket #17574

Open
nh2 opened this issue Jun 17, 2023 · 1 comment
Open

Support for making Nomad listen on Unix Domain Socket #17574

nh2 opened this issue Jun 17, 2023 · 1 comment
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/api HTTP API and SDK issues type/enhancement

Comments

@nh2
Copy link
Contributor

nh2 commented Jun 17, 2023

Use-cases

For testing purposes I wish to start many Nomad servers in parallel.

To avoid port conflicts and running out of ports, I would like to make Nomad listen on Unix Domain Sockets instead of localhost ports.

consul apparently already has Unix Domain Socket support, see docs:

http, https and grpc all support binding to a Unix domain socket. A socket can be specified in the form unix:///path/to/socket. A new domain socket will be created at the given path. If the specified file path already exists, Consul will attempt to clear the file and create the domain socket in its place. The permissions of the socket file are tunable via the unix_sockets config construct.

I would like to do the same with Nomad.

It does not seem to have such support (docs).

Attempted Solutions

# nomad agent -dev -bind 'unix:///tmp/nomad-socket'
==> Failed to parse HTTP advertise address (, unix:///tmp/nomad-socket, 4646, true): Error resolving bind address "unix:///tmp/nomad-socket": lookup unix:///tmp/nomad-socket: no such host
@jrasell
Copy link
Member

jrasell commented Jun 19, 2023

Hi @nh2 and thanks for raising this feature request. I believe this is something we would want to support and which some work has already been conducted for within #16872 and #16884.

@jrasell jrasell added theme/api HTTP API and SDK issues stage/accepted Confirmed, and intend to work on. No timeline committment though. labels Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/api HTTP API and SDK issues type/enhancement
Projects
Status: Needs Roadmapping
Development

No branches or pull requests

2 participants