Description
Some applications have a need to bind to the container's hostname (like Spark) which is different from the NodeManager's hostname(NM_HOST which is available as an env during container launch) when launched through Docker runtime. The container's hostname can be exposed to applications via an env CONTAINER_HOSTNAME. Another potential candidate is the container's IP but this can be addressed in a separate jira.
Attachments
Attachments
Issue Links
- is related to
-
SPARK-23719 Use correct hostname in non-host networking mode in hadoop 3 docker support
- Open