Docker pull new image, but version appears unchanged [solved]

Questions
, , ,
1

Issue

I upgraded my n8n docker image (from 1.73.1 to :latest), using

docker rmi docker.n8n.io/n8nio/n8n:latest
docker image prune  -a
docker pull docker.n8n.io/n8nio/n8n:latest
docker compose down
docker compose up -d

But my logs still show that the version is not changed and held back to 1.73.1. How is this possible, as the image has been fetched correctly?

This does not change even using an explicit tag:

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

Log messages at startup

Permissions 0644 for n8n settings file /home/node/.n8n/config are too wide. 
This is ignored for now, but in the future n8n will attempt to change the permissions automatically. 
To automatically enforce correct permissions now set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true (recommended), 
or turn this check off set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false.
User settings loaded from: /home/node/.n8n/config
Initializing n8n process
n8n ready on 0.0.0.0, port 5678
Version: 1.73.1
 ================================
   Start Active Workflows:
 ================================
   - "ProcessTranscription" (ID: nF1jXsB3w43X15vz)
     => Started

Editor is now accessible via:
http://localhost:5678/

the latest n8n image was pulled, the stack downed and upped again, but the version still remains an old version in th UI.
the docker image is the latest, though

Information on my n8n setup

  • n8n version: 1.73.1 (1.77.3)
  • Database (default: SQLite): postgres 16
  • n8n EXECUTIONS_PROCESS setting (default: own, main): as per docker image
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker compose
  • Operating system: linux ubuntu
2

Also, entering the docker container and checking the version manually returns the 1.73.1 version.

docker compose exec n8n_service ash
> n8n --version
~ $ n8n --version
1.73.1

and /usr/local/lib/node_modules/n8n/package.json is a file with a timestamp at Dec 19th 2024, with version 1.73.1 inside.

3

Solved. There was a problem in the docker-compose.yml, where the node_modules path was mounted as a volume. Once removed, the upgrade was ok.

1 Like