immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-24 11:20:02 +03:00
Code Issues 783 Packages Projects Releases 12 Wiki Activity

[BUG] typesense >=0.24.1 not starting #1007

New Issue
Closed
opened 2026-02-04 23:55:11 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-04 23:55:11 +03:00
Owner
Copy Link

Originally created by @sanasol on GitHub (Jun 26, 2023).

The bug

Fresh(>=0.24.1) typesense image doesn't start, no visible errors or logs.

The OS that Immich Server is running on

Debian GNU/Linux 9.13

Version of Immich Server

v1.63.2

Version of Immich Mobile App

v1.63.2

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

version: "3.8"

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    command: [ "start.sh", "immich" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    command: [ "start.sh", "microservices" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always

  immich-web:
    container_name: immich_web
    image: ghcr.io/immich-app/immich-web:${IMMICH_VERSION:-release}
    env_file:
      - .env
    restart: always

  typesense:
    container_name: immich_typesense
    image: typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd
    environment:
      - TYPESENSE_API_KEY=${TYPESENSE_API_KEY}
      - TYPESENSE_DATA_DIR=/data
    logging:
      driver: none
    volumes:
      - tsdata:/data
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3
    restart: always

  database:
    container_name: immich_postgres
    image: postgres:14-alpine@sha256:28407a9961e76f2d285dc6991e8e48893503cc3836a4755bbc2d40bcc272a441
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      PG_DATA: /var/lib/postgresql/data
    volumes:
      - pgdata:/var/lib/postgresql/data
    restart: always

  immich-proxy:
    container_name: immich_proxy
    image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release}
    environment:
      # Make sure these values get passed through from the env file
      - IMMICH_SERVER_URL
      - IMMICH_WEB_URL
    ports:
      - 2283:8080
    depends_on:
      - immich-server
      - immich-web
    restart: always

volumes:
  pgdata:
  model-cache:
  tsdata:

Your .env content

default

Reproduction steps

1. Start docker-composer with typesene typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd or typesense/typesense:0.24.1
2. Everything started, typesense crashing and in restarting state
3. nothing works

Additional information

Reverted to 0.24.0, its working.

No errors or additional debug with log_level=debug in .env

Only error from typesense is: configured logging driver does not support reading
But this error always appears even when its working.

Originally created by @sanasol on GitHub (Jun 26, 2023). ### The bug Fresh(>=0.24.1) typesense image doesn't start, no visible errors or logs. ### The OS that Immich Server is running on Debian GNU/Linux 9.13 ### Version of Immich Server v1.63.2 ### Version of Immich Mobile App v1.63.2 ### Platform with the issue - [X] Server - [ ] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML version: "3.8" services: immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} command: [ "start.sh", "immich" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env depends_on: - redis - database - typesense restart: always immich-microservices: container_name: immich_microservices image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} command: [ "start.sh", "microservices" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env depends_on: - redis - database - typesense restart: always immich-machine-learning: container_name: immich_machine_learning image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release} volumes: - model-cache:/cache env_file: - .env restart: always immich-web: container_name: immich_web image: ghcr.io/immich-app/immich-web:${IMMICH_VERSION:-release} env_file: - .env restart: always typesense: container_name: immich_typesense image: typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd environment: - TYPESENSE_API_KEY=${TYPESENSE_API_KEY} - TYPESENSE_DATA_DIR=/data logging: driver: none volumes: - tsdata:/data restart: always redis: container_name: immich_redis image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3 restart: always database: container_name: immich_postgres image: postgres:14-alpine@sha256:28407a9961e76f2d285dc6991e8e48893503cc3836a4755bbc2d40bcc272a441 env_file: - .env environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} PG_DATA: /var/lib/postgresql/data volumes: - pgdata:/var/lib/postgresql/data restart: always immich-proxy: container_name: immich_proxy image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release} environment: # Make sure these values get passed through from the env file - IMMICH_SERVER_URL - IMMICH_WEB_URL ports: - 2283:8080 depends_on: - immich-server - immich-web restart: always volumes: pgdata: model-cache: tsdata: ``` ### Your .env content ```Shell default ``` ### Reproduction steps ```bash 1. Start docker-composer with typesene typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd or typesense/typesense:0.24.1 2. Everything started, typesense crashing and in restarting state 3. nothing works ``` ### Additional information Reverted to 0.24.0, its working. No errors or additional debug with log_level=debug in .env Only error from typesense is: configured logging driver does not support reading But this error always appears even when its working.
OVERLORD commented 2026-02-04 23:55:26 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jun 26, 2023):

I think there is issue with Typesense upstream with using older Docker version on some system. If you update your Docker engine, does it help? I think this is Typesense issue instead of Immich

@alextran1502 commented on GitHub (Jun 26, 2023): I think there is issue with Typesense upstream with using older Docker version on some system. If you update your Docker engine, does it help? I think this is Typesense issue instead of Immich
OVERLORD commented 2026-02-04 23:55:28 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jun 26, 2023):

Related information https://github.com/typesense/typesense/issues/1003

@alextran1502 commented on GitHub (Jun 26, 2023): Related information https://github.com/typesense/typesense/issues/1003
OVERLORD commented 2026-02-04 23:55:43 +03:00
Author
Owner
Copy Link

@sanasol commented on GitHub (Jun 26, 2023):

Looks like I have latest possible docker(19.03.15, Jan 30 03:15:40 2021) installation for my ancient server.

@sanasol commented on GitHub (Jun 26, 2023): Looks like I have latest possible docker(19.03.15, Jan 30 03:15:40 2021) installation for my ancient server.
OVERLORD commented 2026-02-04 23:55:47 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jun 26, 2023):

Looks like I have latest possible docker(19.03.15, Jan 30 03:15:40 2021) installation for my ancient server.

You can use 0.24.0 instead

@alextran1502 commented on GitHub (Jun 26, 2023): > Looks like I have latest possible docker(19.03.15, Jan 30 03:15:40 2021) installation for my ancient server. You can use `0.24.0` instead
OVERLORD commented 2026-02-04 23:55:52 +03:00
Author
Owner
Copy Link

@sanasol commented on GitHub (Jun 26, 2023):

Yeah, already running with it.

@sanasol commented on GitHub (Jun 26, 2023): Yeah, already running with it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#1007
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?