You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
@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 -
env {
NOMAD_HOST=$HOSTNAME
}
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.
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.
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: