Cloud Run configuration of n8n

Hello

I have deployed N8N community in cloudrun on GCP .
I want that my service have a peristant volume and cloudrun is a severless option that give as the possibility to mout a volmume on bucket google cloud storage and that is the best way to have data encryption and accessibility .

I mounted it in the configuration of cloud run but there is no data in the bucket .
The problem seem that i have to declare it in n8n , can i use enivronement variable to declare volume ?
If not there is another way to do it .

My question still in this type of deployment i dont want any suggestion of other deployment using vms ; firebase can be accepted .

Thanks

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
  • **n8n version: Version 1.51.1
  • **Database : default SQLite
  • **n8n EXECUTIONS_PROCESS setting :(default: own, main)
  • **Running n8n via : Cloud Run
  • **Operating system: No OS Cloud run is severless i build an image to artifact registry using your docker image

It works fine i can access and do workflows but the problem still in the volume that i want to configure ir with Google Cloud Storage

Hey @Hamza_Ferjeni,

Welcome to the community :cake:

We don’t have a guide available for Cloud Run which means getting n8n working on it with the data will come down to your knowledge of that platform. If it isn’t making the folder I would make sure it is being mounted correctly and in the correct path but it may also be worth remembering that we don’t currently fully support serverless environments so while you don’t want any suggestions for other deployment options it may be the best option for now.

Hey @Jon

Thanks a lot .
is there a possibility to announce a volume in enviroment variable ?

That isn’t really how it works, the application doesn’t control the volume but we do expect you to mount your volume to /home/node/.n8n this path for the user data can be changed with an env option though but the volume will need to be writeable as well.