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

Error re-making Docker image: video-analytics benchmark #334

Open
cg592 opened this issue Oct 25, 2022 · 4 comments
Open

Error re-making Docker image: video-analytics benchmark #334

cg592 opened this issue Oct 25, 2022 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@cg592
Copy link

cg592 commented Oct 25, 2022

Describe the bug
I am trying to (1) run the video-analytics benchmark on other videos that I have uploaded to the video_streaming/reference directory, and also (2) modify the source code to print out additional information. To do so, I believe I need to re-make the Docker image. However, the make all-image command fails when trying to make a new Docker image. The error message mentions needing the GOPRIVATE_KEY I am running the benchmarks locally following the instructions here: https://github.com/vhive-serverless/vSwarm/blob/main/docs/running_locally.md

To Reproduce

cd vSwarm/benchmarks/video-analytics/
make all-image

Expected behavior
Docker image build to complete successfully.

Logs
Output:

DOCKER_BUILDKIT=1 docker build \
-t vhiveease/video-analytics-decoder:latest \
--target decode \
--secret id=GOPRIVATE_KEY \
-f Dockerfile \
../../
could not parse secrets: [id=GOPRIVATE_KEY]: failed to stat GOPRIVATE_KEY: stat GOPRIVATE_KEY: no such file or directory
make: *** [Makefile:34: decoder-image] Error 1

On the instructions page linked above, it says to reach out to obtain the GOPRIVATE_KEY?

@cg592 cg592 added the bug Something isn't working label Oct 25, 2022
@cg592
Copy link
Author

cg592 commented Nov 8, 2022

Any updates on this?

@ustiugov
Copy link
Member

ustiugov commented Nov 8, 2022

@shyamjesal could you please take a look or give advice?

@shyamjesal
Copy link
Collaborator

Hi @cg592,
Building video analytics benchmark requires access to a private repo. Hence the error.
For a workaround, you can try replacing the file in the container. I have not tried it recently, but it should be possible.

@ustiugov
Copy link
Member

@cg592 what you could do is to comment out or stub the xdt dependencies in the source code. it's not an ideal solution but should not be very difficult to do.

Another option is to actually upstream more verbose but configurable logging, e.g., by adding --debug option in the YAML files of the workload, this would be to the benefit of all the users. we would re-build & push containers with your changes

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

3 participants