-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
NOMAD_HOSTNAME env var #538
Comments
@poll0rz We have decided to do this in a generic way So using the env block you will be able to reference Environment Variables that the Nomad client knows about -
So if the Host name environment variable was set in the environment of the Nomad client an user can inject it in his job. That way you can inject any arbitrary environment variable without Nomad core changing. This is also useful in AWS, where you might want to inject the Region, Zone, Ec2 instance id etc. |
#448 should be fixed with this |
hellyeah, this way we can pass a lot of useful info to the task, not only the hostname. |
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. |
Hi,
I think it is useful to have this NOMAD_HOSTNAME env var imported into the Docker containers.
Use case example: a log shipper or a message broker so you can attach the name of the host where the container is running into a "hostname" field.
What do you think? can you make it possible guys? :)
Thank you.
The text was updated successfully, but these errors were encountered: