Stuck on v1.103.2 - Wont update

問題
1

I am using Digital Ocean Droplet, and I have been updating without a problem up until update 1.103.2. I cant seem to update anymore. I am following this to update:

  1. cd /opt/n8n-docker-caddy
  2. docker compose pull
  3. docker compose down
  4. docker compose up -d

When I run console in the droplet and update everything, I don’t get an error or anything but my n8n instance, just doesn’t update. Says I’m 2 updates behind.

Not too sure what I should be adding here, but if anyone can help, that would be helpful.

I am now getting an error with telegram, this is new - not sure if its related:

{69372F97-1618-4411-845D-19601687553D}
{69372F97-1618-4411-845D-19601687553D}343×210 11.8 KB

2

What does your docker-compose.yaml looks like? Does it have the :latest tagged image for n8n?
what is the output of your docker images?

3

@jabbson Here’s my setup for n8n via Docker Compose:

root@n8ninov8:/opt/n8n-docker-caddy# cat docker-compose.yml
version: "3.7"

services:
  caddy:
    image: caddy:latest
    restart: unless-stopped
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - caddy_data:/data
      - ${DATA_FOLDER}/caddy_config:/config
      - ${DATA_FOLDER}/caddy_config/Caddyfile:/etc/caddy/Caddyfile

  n8n:
    image: docker.n8n.io/n8nio/n8n
    restart: always
    ports:
      - 5678:5678
    environment:
      - N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - NODE_ENV=production
      - WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
      - GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
    volumes:
      - n8n_data:/home/node/.n8n
      - ${DATA_FOLDER}/local_files:/files
      
volumes:
  caddy_data:
    external: true
  n8n_data:
    external: true

I’m not explicitly using the :latest tag, but I believe it’s pulling the latest by default.

Output of docker images:

REPOSITORY                TAG       IMAGE ID       CREATED        SIZE
docker.n8n.io/n8nio/n8n   latest    b1b182d75edd   13 days ago    1.02GB
docker.n8n.io/n8nio/n8n   <none>    49c1f771061f   2 weeks ago    1.02GB
docker.n8n.io/n8nio/n8n   <none>    5b172dd544f0   2 weeks ago    1.02GB
docker.n8n.io/n8nio/n8n   <none>    5f88b418e8ce   3 weeks ago    1.02GB
docker.n8n.io/n8nio/n8n   <none>    8cbde8f27083   4 weeks ago    1.01GB
docker.n8n.io/n8nio/n8n   <none>    8b42ec21f2d0   5 weeks ago    1.01GB
docker.n8n.io/n8nio/n8n   <none>    b77d36941bd5   6 weeks ago    1.03GB
docker.n8n.io/n8nio/n8n   <none>    3a6451ffe77f   6 weeks ago    1.03GB
docker.n8n.io/n8nio/n8n   <none>    f0aef05ceceb   7 weeks ago    925MB
docker.n8n.io/n8nio/n8n   <none>    aa464833d710   2 months ago   851MB
docker.n8n.io/n8nio/n8n   <none>    35779977f723   2 months ago   854MB
docker.n8n.io/n8nio/n8n   <none>    2d57503a7ae3   2 months ago   709MB
docker.n8n.io/n8nio/n8n   <none>    46f431c97c42   3 months ago   710MB
caddy                     <none>    14300de7e087   3 months ago   50.5MB
caddy                     latest    6ddf74dfb618   3 months ago   50.5MB
docker.n8n.io/n8nio/n8n   <none>    cb31f87d5a8f   3 months ago   725MB
docker.n8n.io/n8nio/n8n   <none>    10c029c4c947   4 months ago   721MB
docker.n8n.io/n8nio/n8n   <none>    9f9d60171cff   4 months ago   722MB
caddy                     <none>    51f0c496a59a   6 months ago   48.5MB
4

I am pretty sure you will get the 1.103.2, but could you show the output of

docker inspect --format '{{ index .Config.Labels "org.opencontainers.image.version" }}' b1b182d75edd ?

You can remove unused images with docker image prune by the way.

You could try to manually remove the image for 1.103.2 and try to pull the new one to see if that helps.

5

Thanks, I ran the inspect command and confirmed I’m on version 1.103.2.
Also pruned the old images with docker image prune to clean things up.

I tried updating again and it worked! Thank you so much! Did the pruning fix it?

6

Good question, I think it might have, but indirectly. Could the host be running out of space before the old images were pruned?

In any case, if this is solved now, kindly mark the answer as solution, maybe it will help someone else one day. Thanks.