OPIK-663: Pull instead of building Sandbox Python Executor image #1102
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Details
The Sandbox Python Executor image is now pulled instead of being built locally.
The exact registry, name and tag is parameterised as env variables and aligned with the variable names from the Helm charts.
The image is pulled before starting the service as a warm-up. Although this isn't strictly necessary as running a docker container automatically pulls the image if not available locally.
Other improvements in Dockerfile:
tini
to handle zombie sub-processes.Issues
OPIK-663
Testing
Documentation