tdarr_node (docker) won't update to latest 2.18.01 server

[begunfx]

Describe the bug My tdarr server updated last night to the latest version: 2.18.01. My server and remote node are in docker containers. They are both set to get the :latest. However, my tdarr_node doesn't seem to want to update to 2.18.01 and now I get a mis-match error and now cannot deploy the tdarr_node. I tried to force a re-deploy of my tdarr_node but no luck.

tdarr server docker compose:

services:
  tdarr:
    image: ghcr.io/haveagitgat/tdarr:latest
    container_name: tdarr
    hostname: tdarr
    security_opt:
      - no-new-privileges:true
    healthcheck:
      test: wget --no-verbose --tries=1 --spider http://localhost:8265/ || exit 1
    ports:
      - 8265:8265
      - 8266:8266
    environment:
      - TZ=America/Los_Angeles
      - PUID=1034
      - PGID=100
      - serverIP=tdarr
      - serverPort=8266
      - webUIPort=8265
      - internalNode=true
      - nodeID=InternalNode
    volumes:
      - /volume1/docker/tdarr/server:/app/server
      - /volume1/docker/tdarr/configs:/app/configs
      - /volume1/docker/tdarr/logs:/app/logs
      - /volume1/video:/video
      - /volume1/music:/music
      - /volume1/photo:/photo
      - /volume1/docker/tdarr/media:/media
      - /volume1/docker/tdarr/temp:/temp
    restart: always

Here's my tdarr_node docker compose:

services:
  tdarr_node:
    container_name: tdarr_node
    image: ghcr.io/haveagitgat/tdarr_node:latest
    restart: unless-stopped
    network_mode: bridge
    environment:
      - TZ=America/Los_Angeles
      - PUID=1034
      - PGID=100
      - UMASK_SET=002
      - nodeID=DataVaultNode
      - serverIP=Mediavault
      - serverPort=8266
    volumes:

      - /volume1/docker/tdarr/configs:/app/configs
      - /volume1/docker/tdarr/logs:/app/logs
      - /volume1/docker/tdarr/media:/media
      - /volume1/docker/tdarr/temp:/temp

[2024-05-14T07:14:50.874] [ERROR] Tdarr_Server - Node DataVaultNode [ID=-Z-dsILAM] [Address=::ffff:172.27.0.1] [PID=206] - Server version is 2.18.01 but Node version is 2.17.01.

[supersnellehenk]

Have you ran docker compose pull to pull the latest image, then docker compose up -d?

[begunfx]

I was executing the stack from portainer and forcing a re-download and deploy of the latest image.

Update: Seems to have finally updated. Not sure why there was such a delay between the server and node updating but it seems to be working now. Closing this. Thanks!