If you’re using n8n (the popular workflow automation tool) inside a Docker container, regularly updating it is essential to enjoy new features, performance improvements, and security patches.
But updating Docker containers is slightly different from traditional software updates; instead of “upgrading” the app inside the container, we replace the old container with a new one built from the latest image.
In this article, we will guide you through the step-by-step process of updating n8n in Docker, explaining not only what to do but also why each step is important.
Also Read: How to Manually Install n8n on Ubuntu?
Before You Start
Before jumping into commands, let’s make sure you have everything in place.
Prerequisites:
- Docker is already installed and running on your system.
- n8n is currently running in a Docker container.
- You have access to the terminal or SSH for your server.
- You know the name of your n8n container (you can find it using docker ps).
- You’ve backed up your data (we will explain that next).
Also Read: How to Access n8n – A Helpful Guide
Steps to Update n8n in Docker
➢ Step 1: Backup Your n8n Data
Even though Docker makes deployment simple, updating a container replaces the old image, so your data could be lost if it’s stored inside the container itself.
That’s why it’s best to store n8n data in a Docker volume or a bind mount.
If you’re already using a persistent volume (such as /home/n8n/.n8n or/home/node/.n8n), your workflows and credentials are safe.
Still, it’s a good habit to create a backup before updating:
| docker exec -t <container_name> tar czf /home/node/.n8n/backup.tar.gz -C /home/node/.n8n . | Copied!
★ What this does:
➔ docker exec runs a command inside your existing container.
➔ tar czf compresses (create + zip + file) the .n8n folder into a backup file.
➔ /home/node/.n8n is where n8n stores its workflows, credentials, and configurations.
After the command runs, you can copy the backup file to your host machine:
| docker cp <container_name>:/home/node/.n8n/backup.tar.gz . | Copied!
Now you have a safe backup in case something goes wrong.
➢ Step 2: Stop the Running n8n Container
Before pulling a new image, stop your existing container to prevent conflicts:
| docker stop <container_name> | Copied!
★ Why this step?
➔ This ensures n8n doesn’t use files that will soon be replaced.
➔ It gives Docker a clean slate to remove the container safely in the next step.
You can verify it stopped successfully with:
| docker ps | Copied!
If you don’t see your n8n container listed, it’s stopped.
➢ Step 3: Remove the Old Container
Once stopped, remove the old container:
| docker rm <container_name> | Copied!
★ Why this step?
➔ Docker containers are like disposable shells around your application.
➔ Removing the container doesn’t delete your data (as long as it’s stored in a volume).
➔ We remove the old one so Docker can run a fresh container with the latest image version.
➢ Step 4: Pull the Latest n8n Docker Image
Now, let’s get the latest version of n8n from Docker Hub:
| docker pull n8nio/n8n:latest | Copied!
★ What does this?
➔ Docker pull downloads the most recent version of the n8n image.
➔ The :latest tag ensures you’re fetching the newest stable release.
➢ Step 5: Start the New n8n Container
Now, run the new container using your existing configuration.
If you originally ran n8n like this:
| docker run -it –rm \ –name n8n \ -p 5678:5678 \ -v ~/.n8n:/home/node/.n8n \ n8nio/n8n | Copied!
You can use the same command again.
The key part here is the volume mount (-v) — it links your host’s .n8n folder with the container’s data folder, ensuring your workflows remain intact.
Why this step?
➔ docker run creates and starts a new container from the updated image.
➔ The -v option ensures your previous data is reused.
➔ -p maps your system port (5678) to n8n’s internal port.
➔ The –name makes the container easy to reference later.
If you used Docker Compose earlier, you can simply update the image and restart the service:
| docker-compose pull docker-compose up -d | Copied!
This will automatically fetch and run the new image while preserving your volumes and configuration.
➢ Step 6: Verify the Update
To confirm the update was successful, run:
| docker exec -it <container_name> n8n –version | Copied!
You should see the new version number displayed.
You can also open your n8n instance in the browser (e.g., http://localhost:5678) and check the version from the settings.
Also Read: How to Set a Custom Domain for n8n on VPS?
Conclusion
Updating n8n in Docker isn’t complicated; it’s more about understanding how Docker containers work. You’re not ‘upgrading inside’ the container; you’re replacing the old container with a new one built from the latest image.
By following this approach, you can stop the old container, pull the new image, and mount your existing data, ensuring you always stay updated without losing your workflows.
So next time a new n8n release drops, you will know exactly what to do – confidently and safely!