DanielLeens opened a new issue, #11279: URL: https://github.com/apache/seatunnel/issues/11279
## Background The FAQ mentions that users can use scheduling tools such as Apache DolphinScheduler to manage SeaTunnel jobs. Users who deploy SeaTunnel through Docker Compose still need practical guidance for integration details, especially the meaning of `SEATUNNEL_HOME` when the scheduler runs outside or inside a container. A common question is: when SeaTunnel is deployed with Docker Compose, what SeaTunnel home path should be configured in DolphinScheduler? ## Goal Document how to configure DolphinScheduler to submit SeaTunnel jobs when SeaTunnel is deployed with Docker Compose or containerized paths. ## Suggested scope Please add an English and Chinese documentation section or FAQ entry. Possible locations: - `docs/en/faq.md` - `docs/zh/faq.md` - deployment docs under `docs/en/getting-started/` and `docs/zh/getting-started/` The update should explain: 1. What `SEATUNNEL_HOME` means for a scheduler integration. 2. The difference between host paths and container paths. 3. How to decide the correct path when DolphinScheduler runs on the host. 4. How to decide the correct path when DolphinScheduler also runs in Docker or Kubernetes. 5. A minimal example using the common SeaTunnel container path, such as `/opt/seatunnel`, if that is accurate for the current Docker image. 6. Any required volume mounts or network assumptions. ## Acceptance criteria - The docs give a direct answer for Docker Compose deployments. - The docs clearly distinguish host-side and container-side paths. - English and Chinese docs are consistent. - The example is checked against the current SeaTunnel Docker image or Docker Compose deployment docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
