[SPARK-21668] Ability to run driver programs within a container

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.1.1, 2.2.0
• Component/s: Spark Core
• Labels: containers docker driver spark-submit standalone
• Assignee: Unassigned
• Reporter: Arseniy Tashoyan
• Created: 08/Aug/17 11:02
• Updated: 03/Nov/17 09:04
• Resolved: 14/Aug/17 20:47

Description

When a driver program in Client mode runs in a Docker container, it binds to the IP address of the container, not the host machine. This container IP address is accessible only within the host machine, it is inaccessible for master and worker nodes.
For example, the host machine has IP address 192.168.216.10. When Docker machine starts a container, it places it to a special bridged network and assigns it an IP address like 172.17.0.2. All Spark nodes belonging to the 192.168.216.0 network cannot access the bridged network with the container. Therefore, the driver program is not able to communicate with the Spark cluster.
Spark already provides SPARK_PUBLIC_DNS environment variable for this purpose. However, in this scenario setting SPARK_PUBLIC_DNS to the host machine IP address does not work.

Topic on StackOverflow: https://stackoverflow.com/questions/45489248/running-spark-driver-program-in-docker-container-no-connection-back-from-execu

Issue Links

• duplicates: SPARK-6680 Be able to specifie IP for spark-shell(spark driver) blocker for Docker integration
• duplicates: SPARK-4563 Allow spark driver to bind to different ip then advertise ip
• links to: [Github] Pull Request #18885 (tashoyan)