Error When running n8n:latest

Questions
,
21

Using n8n - deployed using Portainer v2.14.2 Business Edition

Today I updated the container to the “latest” version and it immediately started throwing the following error in a loop:

image

I tried the solution, but it didn’t work. Reverted to tag “0.192.2” for now.

docker compose 
version: '3.1'
services:

  postgres:
    image: postgres
    container_name: n8n-postgres

    restart: always
    environment:
      - POSTGRES_USER=${POSTGRES_USER}
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
      - POSTGRES_DB=${POSTGRES_DB}
      - POSTGRES_NON_ROOT_USER=${POSTGRES_NON_ROOT_USER}
      - POSTGRES_NON_ROOT_PASSWORD=${POSTGRES_NON_ROOT_PASSWORD}
    volumes:
      - /var/lib/docker/volumes/n8n/_data/db/data:/var/lib/postgresql/data
      - /var/lib/docker/volumes/n8n/_data/db/init-data.sh:/docker-entrypoint-initdb.d/init-data.sh

    networks:
      - backend

  n8n:
    image: n8nio/n8n:0.192.2
    restart: always
    container_name: n8n
    environment:
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=postgres
      - DB_POSTGRESDB_PORT=5432
      - DB_POSTGRESDB_DATABASE=${POSTGRES_DB}
      - DB_POSTGRESDB_USER=${POSTGRES_NON_ROOT_USER}
      - DB_POSTGRESDB_PASSWORD=${POSTGRES_NON_ROOT_PASSWORD}
      - GENERIC_TIMEZONE=Europe/Prague
      - WEBHOOK_TUNNEL_URL=https://redacted.com      

    links:
      - postgres
    volumes:
      - /var/lib/docker/volumes/n8n/_data/cfg:/home/node/.n8n
      
    # Wait 5 seconds to start n8n to make sure that PostgreSQL is ready when n8n tries to connect to it
    command: /bin/sh -c "sleep 15; n8n start"
    
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.n8n.entrypoints=websecure"
      - 'traefik.http.routers.n8n.rule=Host(`redacted.com`)'
      - "traefik.http.routers.n8n.middlewares=standard@file"
      - 'traefik.docker.network=proxy' # telling traefik to listen to this service on proxy network

    networks:
      - backend
      - proxy
      
networks:
  proxy:
    external: true
  backend:
22

The solution has 2 parts. The update the team pushed and also starting a fresh container.
So create a new container copy over the settings from the old and start it. You can use the same volume.

1 Like
23

Hey @physx911,

What are you currently n8n on? Do you know if it is arm64 or armv7?

24

arm64 on OCI

26

Ok, so tried to update n8n now from 193.1 to 193.3 but had to start a fresh container again.

27

Hey @BramKn,

Yeah we reverted the changes to the working directory and the user, It should be all good from now though.

@physx911 you should should be all good with arm64 now with 0.193.3.

28

@Jon
I read that before yes, But expected the reverted changed to be backwards compatible for some reason. :rofl:

1 Like
29

@BramKn if only it was that easy, I did think a quick symlink could have saved some trouble but we wanted to make sure it was working for arm as well so it was better to just revert and we can do some more test images to make sure we don’t break it again :slight_smile:

1 Like
30

@Jon Do you promise not to break it again? :innocent: