-
Notifications
You must be signed in to change notification settings - Fork 17
P 1398 config and cicd of omni executor #3342
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
Conversation
…-of-omni-executor
…-of-omni-executor
…-of-omni-executor
…-of-omni-executor
…-of-omni-executor
|
@BillyWooo Could you please adjust file-filters / ci job so it rebuilds omni-executor docker image when definition changes ? |
Nvm - I missed target specified in |
Kailai-Wang
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you - do you have the docker running script? Especially about the mounting?
tee-worker/omni-executor/Dockerfile
Outdated
| # WORKDIR $EXECUT_DIR | ||
| ENV HOME=/home/ubuntu | ||
| ENV BUILD_DIR=$HOME/tee-worker/omni-executor | ||
| ENV EXECUT_DIR=/usr/local/bin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean EXECUTOR_DIR, or BIN_DIR?
Yes. In our devops repo. That needs to adjust parameter and test again. |
mainly focus on: build release version omni-executor with gramine.
There was a test release: https://hub.docker.com/layers/litentry/omni-executor/v0.9.25-01/images/sha256-167e5994a871ac8693fc790eb14bcacc977168dee2406c48ac19b27e5dc3d907