corePlugin/dist/plugin.wasm missing in docker image

[danez]

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

• Yes

The bug

I get an error in the logs when the official docker container immich/immich-server:v2.3.1 is starting.

The OS that Immich Server is running on

Raspberry OS with docker 28.5.2

Version of Immich Server

v2.3.1

Version of Immich Mobile App

v2.3.1

Platform with the issue

• Server
• Web
• Mobile

Device make and model

No response

Your docker-compose.yml content

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION}
    volumes:
      - immich-data:/data
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - stack.env
    ports:
      - '8181:2283'
    depends_on:
      - redis
    restart: always
    healthcheck:
      disable: false
    networks:
      default:
      postgres_network:

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION}
    volumes:
      - immich-model-cache:/cache
    env_file:
      - stack.env
    restart: always
    healthcheck:
      disable: false
    networks:
      default:
      postgres_network:

  redis:
    container_name: immich_redis
    image: docker.io/valkey/valkey:8@sha256:81db6d39e1bba3b3ff32bd3a1b19a6d69690f94a3954ec131277b9a26b95b3aa
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always
    networks:
      default:

volumes:
  immich-data:
    name: immich-data
  immich-model-cache:
    name: immich-model-cache

networks:
  default:
    name: immich_network
  postgres_network:
    name: postgres_network
    external: true

Your .env content

IMMICH_VERSION=v2.3.1
DB_URL=<redacted>

Reproduction steps

1. docker compose up

Relevant log output

[Nest] 7  - 11/25/2025, 11:09:46 AM   ERROR [Microservices:Error: ENOENT: no such file or directory, open '/app/immich/data/corePlugin/dist/plugin.wasm'] Failed to load plugin immich-core:

Additional information

immich runs fine so far, so not sure if this is an expected error for now while plugins are being worked on.

[bo0tzz]

Are you sure you're currently running the official image? We don't use /app/immich, but the ImageGenius AIO build does.

[danez]

I just migrated from the imagegenius docker container (run through HAOS) to now use the official one run through portainer.

edit: I guess I need to adapt the path in the db, what should it be?

Or can i remove the db entry and let it recreate?

[f-perna]

I was in the same situation, I deleted my entry and can confirm the core-plugin is still being loaded successfully

immich_server  | [Nest] 39  - 11/26/2025, 9:50:12 PM     LOG [Api:PluginService] Successfully processed core plugin: immich-core (version 2.0.0)
immich_server  | [Nest] 39  - 11/26/2025, 9:50:12 PM     LOG [Api:PluginService] Successfully loaded plugin: immich-core

[haoxi911]

Hi @bo0tzz,

I’m running make dev locally with the latest v2.3.1 codebase. I noticed an error in my console logs:

immich_server | [Nest] 36  - 12/12/2025, 8:56:52 AM   ERROR [Microservices:Error: ENOENT: no such file or directory, open ‘/build/corePlugin/dist/plugin.wasm’] Failed to load plugin immich-core:

When I trace back, it appears that the docker-compose.dev.yml didn’t build the newly added wasm plugins. However, I still see a record of it in the plugin table in the database during app bootstrap.

Is it okay to ignore this error? It seems like the plugin is a new feature that hasn’t been really used yet. Am I correct?

BTW - I believe this is a local-only issue, as I see building scripts in the docker-compose.yml.

[dezhishen]

edit the data in table: plugin
change the wasmPath from /app/immich/data/corePlugin/dist/plugin.wasm to /build/corePlugin/dist/plugin.wasm