devoopsman45 commented on code in PR #1881: URL: https://github.com/apache/datafusion-ballista/pull/1881#discussion_r3444094015
########## docs/source/user-guide/deployment/docker-compose.md: ########## @@ -19,37 +19,51 @@ # Starting a Ballista Cluster using Docker Compose -Docker Compose is a convenient way to launch a cluster when testing locally. +Two Compose files are provided. Choose based on whether you need the last stable release +or want to run against local source changes. -## Build Docker Images +## Option 1: Pre-built images (no local build required) -To create the required Docker images please refer to the [docker deployment page](docker.md). +`docker-compose.quick.yml` pulls images directly from GHCR — no Rust toolchain needed. +Images are published on each stable release; `latest` tracks the most recent release, +not the `main` branch. -## Start a Cluster +```bash +docker compose -f docker-compose.quick.yml up +``` + +See the [quickstart guide](quick-start.md) for connection instructions and data volume setup. -Using the [docker-compose.yml](https://github.com/apache/datafusion-ballista/blob/main/docker-compose.yml) from the -source repository, run the following command to start a cluster: +## Option 2: Build from source + +`docker-compose.yml` builds executor and scheduler images from the local Dockerfiles. +The Dockerfiles copy pre-compiled binaries — they do **not** run `cargo build` themselves. +You must compile first: ```bash -docker-compose up --build +# Step 1 — compile (requires Rust + protoc, takes ~20 min cold) +cargo build --release + +# Step 2 — build Docker images and start the cluster +docker compose up --build ``` -This should show output similar to the following: +Skipping Step 1 will cause the build to fail because the `COPY target/release/ballista-*` +instruction in the Dockerfiles will find no binaries to copy. + +Expected output after a successful start: -```bash -$ docker-compose up -Creating network "ballista-benchmarks_default" with the default driver -Creating ballista-benchmarks_ballista-scheduler_1 ... done -Creating ballista-benchmarks_ballista-executor_1 ... done -Attaching to ballista-benchmarks_ballista-scheduler_1, ballista-benchmarks_ballista-executor_1 -ballista-scheduler_1 | INFO ballista_scheduler: Ballista v52.0.0 Scheduler listening on 0.0.0.0:50050 -ballista-executor_1 | INFO ballista_executor: Ballista v52.0.0 Rust Executor listening on 0.0.0.0:50051 +``` +ballista-scheduler_1 | Ballista Scheduler listening on 0.0.0.0:50050 Review Comment: I am using v2. This is a mistake. It did show ...-N for me. Will edit this. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
