Ensuring Data Persistence in n8n Deployments

I’m running n8n in a Docker container on a Jelastic cloud. Although I configured a volume like my local setup, all workflows and credentials disappear after a restart. Seeking advice.

hey, check if the volume is mappted to the folder n8n really uses. had a similar issue and fixed it by verifying the bind and perssions. hope this helps!

Based on my own experience with n8n deployments in Docker, I found that data persistence issues often stem from minor misconfigurations in mount points or how permissions are set up in your host environment. I resolved similar issues by double-checking the volume mapping configuration in the Docker-compose file and ensuring that the directory inside the container truly aligns with what n8n expects. I also verified the file system permissions, as sometimes the container may write to a temporary directory if it lacks access to the designated persistent volume. In my case, addressing those aspects corrected the issue. Additionally, reviewing the logs helped me isolate any permissions-related errors.