v1.139.2 Docker Container Restart Loop

[allancoding]

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

• Yes

The bug

When I upgraded from v1.138.1 to v1.139.2 the docker container infinity restarts. Downgrading to version v1.139.1 fixes the issue.

The OS that Immich Server is running on

Debian

Version of Immich Server

v1.139.2

Version of Immich Mobile App

v1.139.2

Platform with the issue

• Server
• Web
• Mobile

Device make and model

No response

Your docker-compose.yml content

name: immich
services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    devices:
      - /dev/dri:/dev/dri
    volumes:
      - ${UPLOAD_LOCATION}:/data
      - /mnt/Wilcken:/mnt/wilcken
      - /mnt/Gudmundson:/mnt/gudmundson
      - /mnt/Niles:/mnt/niles
      - /mnt/Public:/mnt/public
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - stack.env
    ports:
      - '2283:2283'
    depends_on:
      - redis
      - database
    restart: unless-stopped
    healthcheck:
      disable: false
    labels:
      - "com.centurylinklabs.watchtower.monitor-only=true"

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - immich-model-cache:/cache
    env_file:
      - stack.env
    restart: unless-stopped
    healthcheck:
      disable: false
    labels:
      - "com.centurylinklabs.watchtower.monitor-only=true"

  redis:
    container_name: immich_redis
    image: docker.io/valkey/valkey:8-bookworm
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always
    volumes:
      - immich-redis:/data
    labels:
      - "com.centurylinklabs.watchtower.monitor-only=true"

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
    volumes:
      - ${DB_DATA_LOCATION}:/var/lib/postgresql/data

    restart: unless-stopped
    labels:
      - "com.centurylinklabs.watchtower.monitor-only=true"

volumes:
  immich-model-cache:
  immich-redis:

Your .env content

UPLOAD_LOCATION=/home/allan/immich/library
DB_DATA_LOCATION=/home/allan/immich/postgres
IMMICH_VERSION=release
DB_PASSWORD=***redacted***
DB_USERNAME=immich
DB_DATABASE_NAME=
IMMICH_PROCESS_INVALID_IMAGES=true

Reproduction steps

1. docker compose up and the immich-server with restart infinity
2. Check the logs

Relevant log output

Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4
Initializing Immich v1.139.2
Detected CPU Cores: 4

Additional information

Going back a version, the server starts up normally.

[alextran1502]

How much RAM do you have allocated for this?

[thomasss02]

Same here. I have Raspberry pi 4 with 8gb RAM. It crash after initialization. Docker container has Unlimited RAM use.

Edit: After downgrading to 1.138.1 and then upgrading to v1.139.2 It works.

[thomasss02]

Perhaps unrelated

[xshyne]

I have the same issue after restarting the server, the new photos i added didn't have thumbnail. I started the job to generate the thumbnail generation and i got this issue of infinite restart.
I got the issue only with photo took from my phone, with screenshot it seems to work normally (the thumbnail is generated correctly).

[allancoding]

How much RAM do you have allocated for this?

16GB on the server. 12GB free

[irfanhakim-as]

Facing the same issue, I thought related to 'corrupted images' bcos images failed to generate thumbnail.. but I don't think that's the 'actual' cause since almost all images I've uploaded since then have all failed to generate thumbnail (when they're really not corrupt at all), and the container keeps restarting when attempting to generate a thumbnail for them.

The server itself is fine, resource usage is very, very free as it's been before.

More of my reports/logs are on this issue: #16044 (comment)

---

Update: can confirm that downgrading to the previous version, v1.138.1, solves the issue completely.

[schuettecarsten]

I had the same issue. For me it was related by assets that cannot be converted/processed by thumbnail generator causing a crash of the whole docker image.

[allancoding]

Updating to v1.139.3 solved the issue for me.

[skatsubo]

@irfanhakim-as @schuettecarsten @xshyne Could you share an image that triggers the issue?

Probably caused by immich-app/base-images#259 and we'd like to see if the most recent libheif fixes it or do we need to rollback.

[irfanhakim-as]

It was happening to me consistently on version v1.139.2@sha256:6bd954809e2ddd0e5557b3a57031255f88b1b1b20e90f4354c5c5bffca91d9af (assuming this was what you were asking, its image tag). The issue's gone since downgrading back to v1.138.1@sha256:ec0bb170125d404c8965a90fba0a1f654927e36423585bcc1ff8625211d4a9be.

[allancoding]

It was happening to me consistently on version v1.139.2@sha256:6bd954809e2ddd0e5557b3a57031255f88b1b1b20e90f4354c5c5bffca91d9af (assuming this was what you were asking, its image tag). The issue's gone since downgrading back to v1.138.1@sha256:ec0bb170125d404c8965a90fba0a1f654927e36423585bcc1ff8625211d4a9be.

Same here.

[skatsubo]

@irfanhakim-as Ah, sorry, I meant sharing the photo. If the issue is triggered by thumbnail generation for a particular image.