Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker build fails #589

Closed
hokiegeek2 opened this issue Jan 8, 2023 · 3 comments
Closed

docker build fails #589

hokiegeek2 opened this issue Jan 8, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@hokiegeek2
Copy link

hokiegeek2 commented Jan 8, 2023

Describe the bug
Attempted to build the ballista docker images using the instructions [here](git clone [email protected]:apache/arrow-ballista.git -b 0.9.0). When I ran ./dev/build-ballista-docker.sh the first image, ballista-builder built fine:

image

however, the ballista-scheduler image build fails:

image

To Reproduce
Per the docker build instructions:

git clone [email protected]:apache/arrow-ballista.git -b 0.9.0
cd arrow-ballista
./dev/build-ballista-docker.sh

Expected behavior
Per the instructions, expect to see the arrow-ballista-scheduler and arrow-ballista-executor images to build.

Additional context
Running docker build on ubuntu 22.04

@hokiegeek2 hokiegeek2 added the bug Something isn't working label Jan 8, 2023
@hokiegeek2
Copy link
Author

ah, okay, looking at the examples/README, the target/release files need to be built first:

cargo build --release

However, when I execute this command, I get the following error:

image

@hokiegeek2
Copy link
Author

hokiegeek2 commented Jan 8, 2023

I was, however, able to build the ballista-scheduler and ballista-execute binaries via the following commands specified here

cargo install --locked ballista-scheduler
cargo install --locked ballista-executor

Note: I had to install protobuf-compiler to get the installs to work after seeing this error:

image

binaries available:

image

able to run scheduler:

image

@hokiegeek2
Copy link
Author

closing this as I figured out it is due to the target/ballista-scheduler missing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant