Add CACHE_DIR to allow moving cache location#882
Open
akiller wants to merge 2 commits intoHumanSignal:masterfrom
Open
Add CACHE_DIR to allow moving cache location#882akiller wants to merge 2 commits intoHumanSignal:masterfrom
akiller wants to merge 2 commits intoHumanSignal:masterfrom
Conversation
Author
I have now tried this on Azure and it does work with this fix. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently the model cache file is written to the location of the
MODEL_DIRenvironment variable if set.I want to deploy the label studio ML backend to an Azure container app. My model is persisted to an Azure storage file share mounted at /app/models and so my
MODEL_DIRis set to /app/models.But Azure files don't work with Sqlite database, and it will error with
Error: SQLITE_BUSY: database is lockedI want to add a new
CACHE_DIRenvironment variable which will allow the cache to be moved to an alternative location inside the container which should fix my problem.If not set, it will fallback to using
MODEL_DIRso it shouldn't cause any problems for existing users.I haven't tested this (sorry!).