Closed parbatrajpurohit closed 2 weeks ago
The issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a specific scenario that is not easy to reproduce on our side.
If you think that's not the case and are interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.
With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Name and Version
bitnami/spark:3.5.1
What is the problem this feature will solve?
Description: I am trying to set up a Spark cluster using Docker Compose with the following services:
spark-master spark-connect spark-worker spark-worker2
The Docker Compose file I am using is as follows:
What is the feature you are proposing to solve the problem?
I need to run a custom script (run.sh) along with the start-connect-server.sh service. However, I am unsure how to modify the command section in the spark-connect service to achieve this.
Expected Solution: