You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm attempting to deploy the FlowiseAI Docker image on Google Cloud Run, primarily due to its cost-effectiveness with auto-scaling capabilities.
However, I'm encountering an issue: When auto-scaling scales the container down to zero (sleep mode) and then scales back up, I notice that PDF-related packages appear to be missing or uninstalled. I'm also experiencing other related issues with the container state not persisting properly.
My question is: How can I properly configure persistent volumes with Google Cloud Run for the FlowiseAI Docker image to maintain the installed packages and container state across scaling events?
Any guidance or best practices for handling stateful components in FlowiseAI on Cloud Run would be greatly appreciated.
Environment:
Platform: Google Cloud Run Application: FlowiseAI (Docker image) Issue: Package persistence during auto-scaling
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I'm attempting to deploy the FlowiseAI Docker image on Google Cloud Run, primarily due to its cost-effectiveness with auto-scaling capabilities.
However, I'm encountering an issue: When auto-scaling scales the container down to zero (sleep mode) and then scales back up, I notice that PDF-related packages appear to be missing or uninstalled. I'm also experiencing other related issues with the container state not persisting properly.
My question is: How can I properly configure persistent volumes with Google Cloud Run for the FlowiseAI Docker image to maintain the installed packages and container state across scaling events?
Any guidance or best practices for handling stateful components in FlowiseAI on Cloud Run would be greatly appreciated.
Environment:
Platform: Google Cloud Run
Application: FlowiseAI (Docker image)
Issue: Package persistence during auto-scaling
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions