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 .
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.
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.
We are looking into hosting n8n on CloudRun.
Have you run into issues like hibernation? Any other issues?
Have you been able to resolve the volume mount issue?
I’m also trying to run it in Cloud Run. I’m able to easily mount GCS bucket, but during startup I see this warning:
Permissions 0666 for n8n settings file /home/node/.n8n/config are too wide. This is ignored for now, but in the future n8n will attempt to change the permissions automatically. To automatically enforce correct permissions now set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true (recommended), or turn this check off set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false.
Not sure if it impacts it anyhow, but the service doesn’t start with the error:
Ok, that was issue on my side. I’ve fixed it, and now I’m facing these errors:
User settings loaded from: /home/node/.n8n/config
(node:9) Warning: TypeError
module: @oclif/[email protected]
task: findCommand (audit)
plugin: n8n
root: /usr/local/lib/node_modules/n8n
message: Cannot read properties of undefined (reading 'database')
See more details with DEBUG=*
› Error: command start not found
Container called exit(2).
