Multistage build with baked-in models needed for the enabled guardrails #12
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.
Description
Dockerfile server (
Dockerfile.server)ARG GUARDRAILS_PROFILE; when ARG GUARDRAILS_PROFILE is set to "opensource", closed source guardrails as specified inscripts/provider-list.yamlare removed; when ARG GUARDRAILS_PROFILE is set to "all", there is no removalscripts/discover_required_models.pyandpre_download_required_models.py) which attempt to find which models are being used by the guardrails; then these models are downloaded inside the imagepyproject.tomlTest
Ran this small demo: https://github.com/m-misiura/demos/tree/main/nemo_openshift with the following image: quay.io/rh-ee-mmisiura/nemo-guardrails:os_profile_with_models