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

[FEATURE]: Add custom DNS options for the exec driver #7283

Closed
danlsgiga opened this issue Mar 6, 2020 · 5 comments · Fixed by #7661
Closed

[FEATURE]: Add custom DNS options for the exec driver #7283

danlsgiga opened this issue Mar 6, 2020 · 5 comments · Fixed by #7661

Comments

@danlsgiga
Copy link
Contributor

Right now the exec driver does not provide a way to specify custom DNS servers for the task.

Just like the docker driver has the --dns-* options, it would be great to be able to provide custom DNS settings for exec task drivers.

I thought on setting "/opt/custom_resolv.conf" = "/etc/resolv.conf" in the chroot_env settings for the nomad clients but I'm not 100% sure it works.

@danlsgiga danlsgiga changed the title [FEATURE]: [FEATURE]: Add custom DNS options for the exec driver Mar 6, 2020
@notnoop
Copy link
Contributor

notnoop commented Mar 27, 2020

Thanks @danlsgiga Sorry for taking forever to get back.

This is related to #7393 and we may address these together.

@danlsgiga
Copy link
Contributor Author

This is related to #7283 and we may address these together.

Maybe there's a typo here... 7283 is this issue! :)

@notnoop
Copy link
Contributor

notnoop commented Mar 27, 2020

🤦‍♂ Oops. Sorry. I meant #7393

@nickethier nickethier mentioned this issue Apr 8, 2020
9 tasks
@danlsgiga
Copy link
Contributor Author

Closing this in favour of #7393

@github-actions
Copy link

github-actions bot commented Nov 5, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants