License persistence when updating N8N self hosted instance

Questions
1

Describe the problem/error/question

I have a self-hosted n8n instance that I deploy with docker compose.

Every time I update the instance, I delete all belonging to the docker compose file, including the volumes.

From other comments in the forum, I understand that because I have a volume mapped to /home/node/.n8n in the container, then this is the reason that forces me to re-enter the license information again.

Shall I keep that volume if I want to avoid having to enter the license again after re-creating the container?

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.77.3
  • Database (default: SQLite): Postgres database
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu 24.10
2

Yes, you should make a persistent volume for that and to keep your data safe in case you need to reboot or update.

I use Coolify to manage my containers and it’s awesome. You might find it useful.

:muscle: If my reply answers your question, please remember to mark it as a solution.

3

Thank you @solomon for your answer.

I tried Coolify when I started with n8n some weeks ago, but the application did not start.

I realized that the issue was to use Portainer to deploy and update the services in my docker compose file.
If I update without deleting the volumes, then the services do not start correctly with Portainer, but if I delete the volumes, then I have to enter the license again.
I am using now the docker compose commands directly.

4

I see. So now you can keep your data when you update?
If I delete my volume I lose my workflows and credentials.