How to Update n8n Version (Docker, Oracle Cloud, Desktop)

Automation
How to Update n8n Version (Docker, Oracle Cloud, Desktop)

How to Update n8n Version (Docker, Oracle Cloud, Desktop)

Keeping your automation platform updated is crucial for security and accessing new features (like recent AI capabilities). Here is the definitive guide on how to update n8n version across different environments.

1. Updating n8n on Docker (Standard)

If you followed the standard Docker setup, updating is simple.

Step 1: Stop the container

docker stop n8n

Step 2: Remove the old container (Don’t worry, your data is safe if you used a volume!)

docker rm n8n

Step 3: Pull the latest image

docker pull docker.n8n.io/n8nio/n8n:latest

Step 4: Restart the container Run your original start command again. Example:

docker run -d --name n8n -p 5678:5678 -v n8n_data:/home/node/.n8n docker.n8n.io/n8nio/n8n:latest

2. Updating n8n on Docker Compose

This is the most common method for self-hosters.

  1. Navigate to your n8n directory: 
    cd /path/to/n8n
  2. Pull the latest images: 
    docker-compose pull
  3. Recreate the containers: 
    docker-compose up -d
  4. Clear unused images (optional): 
    docker image prune -f

3. Updating n8n on Oracle Cloud (Free Tier)

Many users run n8n on Oracle Cloud due to its generous free tier. The process is the same as Docker/Docker Compose above, but with a few caveats:

Important Checks:

  • Backup: Always snapshot your instance before updating.
  • Architecture: Ensure you pull the correct image for ARM (Ampere) instances if applicable, though n8n’s multi-arch image usually handles this.

4. Updating n8n Desktop App

The desktop app handles updates differently.

  • Mac/Windows: When a new version is available, you should see a prompt inside the application.
  • Manual: simply download the latest installer from the n8n website and install it over the existing version. Your workflows are stored in ~/.n8n and remain safe.

If you installed via npm:

npm update -g n8n

Note: npm installations are harder to maintain and rollback compared to Docker.

Troubleshooting Updates

“Database Migration Failed” If an update fails due to DB issues, roll back to the previous version immediately by specifying the tag (e.g., n8nio/n8n:1.0.0) instead of latest, and check the release notes for breaking changes.

“Workflows Missing” This usually means you didn’t mount your volume correctly when restarting the container. Ensure -v n8n_data:/home/node/.n8n matches your original setup.

Conclusion

Regularly knowing how to update n8n version ensures you have the latest drivers, security patches, and AI nodes. We recommend updating monthly or when major features drop.

Related Posts