I’m running n8n in a Docker container on a cloud hosting service using Jelastic. Even after setting up a volume for persistence, my workflows and credentials vanish on container restart. Any advice?
I had a similar issue when setting up persistent storage for n8n. What helped me was double checking that my volume mounts were actually pointing to the correct n8n data directory. I also discovered that environment variables related to database paths need to be set explicitly so that the container uses the external volume instead of internal storage. In my case, adjusting the container settings and verifying the permissions on the cloud host for the mounted volume solved the problem. I recommend reviewing your Docker settings and paths carefully.
hey, i ran into this too. my fix was reconfiguring my docker-compose and ensuring the volume’s path and permissions were right, plus tweaking a few env settings. sometimes a full container restart cks the issue. hope this helps!
Based on my experience, ensuring persistent data storage in n8n involves not only mapping the correct directory but also configuring environment variables so that n8n uses the external volume for data storage. I faced issues where the working directory was not properly directed to the mounted volume, which caused data loss upon container restart. Reviewing the logs and verifying that the volume holds the expected content can help. It’s useful to consider adjustments in both the Docker settings and in the n8n configuration to sustain all workflows and credentials.
I encountered a similar problem when trying to implement persistent storage with n8n in a Docker environment. My challenge was sorting out the correct directory mapping in the container configuration. I discovered that small mistakes in the mount points or not adjusting the default file paths led to data being stored in the container’s ephemeral storage rather than on the persistent volume. After reviewing my Dockerfile and verifying that all environmental variables were correctly set, I resolved the data loss issue. Checking the container logs and file permissions also played a key role in troubleshooting this problem.