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

immich_server and _microservices keeps rebooting every minute - Synology DS920+ docker #2170

New Issue
Closed
opened 2026-02-05 05:26:09 +03:00 by OVERLORD · 18 comments
OVERLORD commented 2026-02-05 05:26:09 +03:00
Owner
Copy Link

Originally created by @Georgie2323 on GitHub (Feb 17, 2024).

The bug

DS920+ install using docker compose - Was able to get install but two of my five containers keep rebooting and I cannot log into the webserver. I have opened the port on firewall and have a standard install.

The OS that Immich Server is running on

Synology DSM 7.2.1

Version of Immich Server

1.94.1

Version of Immich Mobile App

not using

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

version: "3.8"

#
# WARNING: Make sure to use the docker-compose.yml of the current release:
#
# https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
#
# The compose file on main may not be compatible with the latest release.
#

name: immich

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
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    ports:
      - 2283:3001
    depends_on:
      - redis
      - database
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/hardware-transcoding
    #   file: hwaccel.transcoding.yml 
    #   service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
    command: [ "start.sh", "microservices" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    depends_on:
      - redis
      - database
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    # For hardware acceleration, add one of -[armnn, cuda, openvino] to the image tag.
    # Example tag: ${IMMICH_VERSION:-release}-cuda
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration
    #   file: hwaccel.ml.yml
    #   service: cpu # set to one of [armnn, cuda, openvino, openvino-wsl] for accelerated inference - use the `-wsl` version for WSL2 where applicable
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always

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

  database:
    container_name: immich_postgres
    image: tensorchord/pgvecto-rs:pg14-v0.1.11@sha256:0335a1a22f8c5dd1b697f14f079934f5152eaaa216c09b61e293be285491f8ee
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
    volumes:
      - pgdata:/var/lib/postgresql/data
    restart: always

volumes:
  pgdata:
  model-cache:

Your .env content

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION=./library

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release

# Connection secret for postgres. You should change it to a random password
DB_PASSWORD=xxxxxxxxxxxxx

# The values below this line do not need to be changed
###################################################################################
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

REDIS_HOSTNAME=immich_redis

Reproduction steps

1. Open container and get it running
2.
3.
...

Additional information

I have opened ports
I have rebooted the NAS and reinstalled multiple times with same error
Screenshot 2024-02-17 at 9 43 08 am
Screenshot 2024-02-17 at 10 42 41 am

Originally created by @Georgie2323 on GitHub (Feb 17, 2024). ### The bug DS920+ install using docker compose - Was able to get install but two of my five containers keep rebooting and I cannot log into the webserver. I have opened the port on firewall and have a standard install. ### The OS that Immich Server is running on Synology DSM 7.2.1 ### Version of Immich Server 1.94.1 ### Version of Immich Mobile App not using ### Platform with the issue - [X] Server - [x] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML version: "3.8" # # WARNING: Make sure to use the docker-compose.yml of the current release: # # https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml # # The compose file on main may not be compatible with the latest release. # name: immich 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 - /etc/localtime:/etc/localtime:ro env_file: - .env ports: - 2283:3001 depends_on: - redis - database restart: always immich-microservices: container_name: immich_microservices image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/hardware-transcoding # file: hwaccel.transcoding.yml # service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding command: [ "start.sh", "microservices" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload - /etc/localtime:/etc/localtime:ro env_file: - .env depends_on: - redis - database restart: always immich-machine-learning: container_name: immich_machine_learning # For hardware acceleration, add one of -[armnn, cuda, openvino] to the image tag. # Example tag: ${IMMICH_VERSION:-release}-cuda image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release} # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration # file: hwaccel.ml.yml # service: cpu # set to one of [armnn, cuda, openvino, openvino-wsl] for accelerated inference - use the `-wsl` version for WSL2 where applicable volumes: - model-cache:/cache env_file: - .env restart: always redis: container_name: immich_redis image: redis:6.2-alpine@sha256:afb290a0a0d0b2bd7537b62ebff1eb84d045c757c1c31ca2ca48c79536c0de82 restart: always database: container_name: immich_postgres image: tensorchord/pgvecto-rs:pg14-v0.1.11@sha256:0335a1a22f8c5dd1b697f14f079934f5152eaaa216c09b61e293be285491f8ee env_file: - .env environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} volumes: - pgdata:/var/lib/postgresql/data restart: always volumes: pgdata: model-cache: ``` ### Your .env content ```Shell # You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables # The location where your uploaded files are stored UPLOAD_LOCATION=./library # The Immich version to use. You can pin this to a specific version like "v1.71.0" IMMICH_VERSION=release # Connection secret for postgres. You should change it to a random password DB_PASSWORD=xxxxxxxxxxxxx # The values below this line do not need to be changed ################################################################################### DB_HOSTNAME=immich_postgres DB_USERNAME=postgres DB_DATABASE_NAME=immich REDIS_HOSTNAME=immich_redis ``` ### Reproduction steps ```bash 1. Open container and get it running 2. 3. ... ``` ### Additional information I have opened ports I have rebooted the NAS and reinstalled multiple times with same error <img width="1090" alt="Screenshot 2024-02-17 at 9 43 08 am" src="https://github.com/immich-app/immich/assets/106001776/72282878-65c6-416f-9e30-6554f79798e9"> <img width="1426" alt="Screenshot 2024-02-17 at 10 42 41 am" src="https://github.com/immich-app/immich/assets/106001776/5d464908-79f6-4e18-afa0-7c7c47ab3c70">
OVERLORD commented 2026-02-05 05:26:21 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Feb 17, 2024):

If I remember correctly, the current database version doesn't support the kernel version on Synology NAS. The next release will include the version that is supported on Synology

@alextran1502 commented on GitHub (Feb 17, 2024): If I remember correctly, the current database version doesn't support the kernel version on Synology NAS. The next release will include the version that is supported on Synology
OVERLORD commented 2026-02-05 05:26:25 +03:00
Author
Owner
Copy Link

@Georgie2323 commented on GitHub (Feb 17, 2024):

ok thank you - I will wait for the next version

@Georgie2323 commented on GitHub (Feb 17, 2024): ok thank you - I will wait for the next version
OVERLORD commented 2026-02-05 05:26:33 +03:00
Author
Owner
Copy Link

@bo0tzz commented on GitHub (Feb 17, 2024):

#5893

@bo0tzz commented on GitHub (Feb 17, 2024): #5893
OVERLORD commented 2026-02-05 05:26:36 +03:00
Author
Owner
Copy Link

@Georgie2323 commented on GitHub (Mar 5, 2024):

I have upgraded to new versions and still having same problems - will keep waiting for fix?

@Georgie2323 commented on GitHub (Mar 5, 2024): I have upgraded to new versions and still having same problems - will keep waiting for fix?
OVERLORD commented 2026-02-05 05:26:38 +03:00
Author
Owner
Copy Link

@projek01 commented on GitHub (Mar 5, 2024):

After messing with this for days (had no luck with the other suggestions). I did the following which worked.
USE AT YOUR OWN RISK.
Backed up the immich docker folder to another location.
Stopped the container, cleaned then deleted.
Updated config yml to the newest version.
Deleted everything in the model-cache and pgdata folder.
Reinstalled the container.
Signed into immich but saw no photos or albums.
Stop the container.
Copy (overwrite) everything in the model-cache to pgdata backup to the working immich folder.
Restart immich.

@projek01 commented on GitHub (Mar 5, 2024): After messing with this for days (had no luck with the other suggestions). I did the following which worked. USE AT YOUR OWN RISK. Backed up the immich docker folder to another location. Stopped the container, cleaned then deleted. Updated config yml to the newest version. Deleted everything in the model-cache and pgdata folder. Reinstalled the container. Signed into immich but saw no photos or albums. Stop the container. Copy (overwrite) everything in the model-cache to pgdata backup to the working immich folder. Restart immich.
OVERLORD commented 2026-02-05 05:26:46 +03:00
Author
Owner
Copy Link

@Georgie2323 commented on GitHub (Mar 5, 2024):

I am not getting anything other than a library folder created that I created
The model-cache and pgdata folder are not created so not sure what I am doing wrong

@Georgie2323 commented on GitHub (Mar 5, 2024): I am not getting anything other than a library folder created that I created The model-cache and pgdata folder are not created so not sure what I am doing wrong
OVERLORD commented 2026-02-05 05:26:59 +03:00
Author
Owner
Copy Link

@projek01 commented on GitHub (Mar 5, 2024):

I am not getting anything other than a library folder created that I created The model-cache and pgdata folder are not created so not sure what I am doing wrong

The folders are created manually by yourself. I just deleted everything inside the two folders -> delete the container ->clean unused images -> reinstall using new yaml (same .env) ->logged in -> stopped the container -> copied the contents from the backup into model-cache and pgdata choosing the "overwrite" option -> restarted immich.

@projek01 commented on GitHub (Mar 5, 2024): > I am not getting anything other than a library folder created that I created The model-cache and pgdata folder are not created so not sure what I am doing wrong The folders are created manually by yourself. I just deleted everything inside the two folders -> delete the container ->clean unused images -> reinstall using new yaml (same .env) ->logged in -> stopped the container -> copied the contents from the backup into model-cache and pgdata choosing the "overwrite" option -> restarted immich.
OVERLORD commented 2026-02-05 05:27:03 +03:00
Author
Owner
Copy Link

@UndercoverNerd5 commented on GitHub (May 10, 2024):

So which folders need to be created?!

@UndercoverNerd5 commented on GitHub (May 10, 2024): So which folders need to be created?!
OVERLORD commented 2026-02-05 05:27:08 +03:00
Author
Owner
Copy Link

@Georgie2323 commented on GitHub (Jul 21, 2024):

Hi I have continuously been trying and still getting the same error where the immich server keeps rebooting every minute
Has anything changed that might have fixed this or is there any other things I can try

@Georgie2323 commented on GitHub (Jul 21, 2024): Hi I have continuously been trying and still getting the same error where the immich server keeps rebooting every minute Has anything changed that might have fixed this or is there any other things I can try
OVERLORD commented 2026-02-05 05:27:14 +03:00
Author
Owner
Copy Link

@Georgie2323 commented on GitHub (Jul 21, 2024):

date stream content
2024/07/21 19:34:31 stderr }
2024/07/21 19:34:31 stderr syscall: 'connect'
2024/07/21 19:34:31 stderr code: 'ETIMEDOUT',
2024/07/21 19:34:31 stderr errorno: 'ETIMEDOUT',
2024/07/21 19:34:31 stderr at process.processTimers (node:internal/timers:514:7) {
2024/07/21 19:34:31 stderr at listOnTimeout (node:internal/timers:573:17)
2024/07/21 19:34:31 stderr at Socket._onTimeout (node:net:590:8)
2024/07/21 19:34:31 stderr at Socket.emit (node:events:519:28)
2024/07/21 19:34:31 stderr at Object.onceWrapper (node:events:633:28)
2024/07/21 19:34:31 stderr at Socket. (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41)
2024/07/21 19:34:31 stderr Error: connect ETIMEDOUT
2024/07/21 19:34:31 stderr }
2024/07/21 19:34:31 stderr syscall: 'connect'
2024/07/21 19:34:31 stderr code: 'ETIMEDOUT',
2024/07/21 19:34:31 stderr errorno: 'ETIMEDOUT',
2024/07/21 19:34:31 stderr at process.processTimers (node:internal/timers:514:7) {
2024/07/21 19:34:31 stderr at listOnTimeout (node:internal/timers:573:17)
2024/07/21 19:34:31 stderr at Socket._onTimeout (node:net:590:8)
2024/07/21 19:34:31 stderr at Socket.emit (node:events:519:28)
2024/07/21 19:34:31 stderr at Object.onceWrapper (node:events:633:28)
2024/07/21 19:34:31 stderr at Socket. (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41)
2024/07/21 19:34:31 stderr Error: connect ETIMEDOUT
2024/07/21 19:34:31 stderr }
2024/07/21 19:34:31 stderr syscall: 'connect'
2024/07/21 19:34:31 stderr code: 'ETIMEDOUT',
2024/07/21 19:34:31 stderr errorno: 'ETIMEDOUT',
2024/07/21 19:34:31 stderr at process.processTimers (node:internal/timers:514:7) {
2024/07/21 19:34:31 stderr at listOnTimeout (node:internal/timers:573:17)
2024/07/21 19:34:31 stderr at Socket._onTimeout (node:net:590:8)
2024/07/21 19:34:31 stderr at Socket.emit (node:events:519:28)
2024/07/21 19:34:31 stderr at Object.onceWrapper (node:events:633:28)
2024/07/21 19:34:31 stderr at Socket. (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41)
2024/07/21 19:34:31 stderr Error: connect ETIMEDOUT
2024/07/21 19:34:31 stderr }
@Georgie2323 commented on GitHub (Jul 21, 2024): date | stream | content -- | -- | -- 2024/07/21 19:34:31 | stderr | } 2024/07/21 19:34:31 | stderr | syscall: 'connect' 2024/07/21 19:34:31 | stderr | code: 'ETIMEDOUT', 2024/07/21 19:34:31 | stderr | errorno: 'ETIMEDOUT', 2024/07/21 19:34:31 | stderr | at process.processTimers (node:internal/timers:514:7) { 2024/07/21 19:34:31 | stderr | at listOnTimeout (node:internal/timers:573:17) 2024/07/21 19:34:31 | stderr | at Socket._onTimeout (node:net:590:8) 2024/07/21 19:34:31 | stderr | at Socket.emit (node:events:519:28) 2024/07/21 19:34:31 | stderr | at Object.onceWrapper (node:events:633:28) 2024/07/21 19:34:31 | stderr | at Socket.<anonymous> (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41) 2024/07/21 19:34:31 | stderr | Error: connect ETIMEDOUT 2024/07/21 19:34:31 | stderr | } 2024/07/21 19:34:31 | stderr | syscall: 'connect' 2024/07/21 19:34:31 | stderr | code: 'ETIMEDOUT', 2024/07/21 19:34:31 | stderr | errorno: 'ETIMEDOUT', 2024/07/21 19:34:31 | stderr | at process.processTimers (node:internal/timers:514:7) { 2024/07/21 19:34:31 | stderr | at listOnTimeout (node:internal/timers:573:17) 2024/07/21 19:34:31 | stderr | at Socket._onTimeout (node:net:590:8) 2024/07/21 19:34:31 | stderr | at Socket.emit (node:events:519:28) 2024/07/21 19:34:31 | stderr | at Object.onceWrapper (node:events:633:28) 2024/07/21 19:34:31 | stderr | at Socket.<anonymous> (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41) 2024/07/21 19:34:31 | stderr | Error: connect ETIMEDOUT 2024/07/21 19:34:31 | stderr | } 2024/07/21 19:34:31 | stderr | syscall: 'connect' 2024/07/21 19:34:31 | stderr | code: 'ETIMEDOUT', 2024/07/21 19:34:31 | stderr | errorno: 'ETIMEDOUT', 2024/07/21 19:34:31 | stderr | at process.processTimers (node:internal/timers:514:7) { 2024/07/21 19:34:31 | stderr | at listOnTimeout (node:internal/timers:573:17) 2024/07/21 19:34:31 | stderr | at Socket._onTimeout (node:net:590:8) 2024/07/21 19:34:31 | stderr | at Socket.emit (node:events:519:28) 2024/07/21 19:34:31 | stderr | at Object.onceWrapper (node:events:633:28) 2024/07/21 19:34:31 | stderr | at Socket.<anonymous> (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41) 2024/07/21 19:34:31 | stderr | Error: connect ETIMEDOUT 2024/07/21 19:34:31 | stderr | }
OVERLORD commented 2026-02-05 05:27:20 +03:00
Author
Owner
Copy Link

@fluentnumbers commented on GitHub (Sep 25, 2024):

still experience this issue. When I switch off the firewall on my synology, the connection goes through, but swithing firewall back breaks it again.

@fluentnumbers commented on GitHub (Sep 25, 2024): still experience this issue. When I switch off the firewall on my synology, the connection goes through, but swithing firewall back breaks it again.
OVERLORD commented 2026-02-05 05:27:25 +03:00
Author
Owner
Copy Link

@unickq commented on GitHub (Oct 7, 2024):

same here :(
tested with both firewall on and off.

@unickq commented on GitHub (Oct 7, 2024): same here :( tested with both firewall on and off.
OVERLORD commented 2026-02-05 05:27:30 +03:00
Author
Owner
Copy Link

@fluentnumbers commented on GitHub (Oct 7, 2024):

still experience this issue. When I switch off the firewall on my synology, the connection goes through, but swithing firewall back breaks it again.

I solved the issue by adding the immich Docker network ip address to the list of firewall rules

@fluentnumbers commented on GitHub (Oct 7, 2024): > still experience this issue. When I switch off the firewall on my synology, the connection goes through, but swithing firewall back breaks it again. I solved the issue by adding the immich Docker network ip address to the list of firewall rules
OVERLORD commented 2026-02-05 05:27:33 +03:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 21, 2024):

still experience this issue. When I switch off the firewall on my synology, the connection goes through, but swithing firewall back breaks it again.

I solved the issue by adding the immich Docker network ip address to the list of firewall rules

Do you still remember which ip address you added?

@ghost commented on GitHub (Nov 21, 2024): > > still experience this issue. When I switch off the firewall on my synology, the connection goes through, but swithing firewall back breaks it again. > > I solved the issue by adding the immich Docker network ip address to the list of firewall rules Do you still remember which ip address you added?
OVERLORD commented 2026-02-05 05:27:39 +03:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 21, 2024):

still experience this issue. When I switch off the firewall on my synology, the connection goes through, but swithing firewall back breaks it again.

I solved the issue by adding the immich Docker network ip address to the list of firewall rules

Do you still remember which ip address you added?

It turns out you should go to Container Manager and check all 4 instances of Immich and open the ports in your firewall rules. For me, they were 172.22.0.X.

@ghost commented on GitHub (Nov 21, 2024): > > > still experience this issue. When I switch off the firewall on my synology, the connection goes through, but swithing firewall back breaks it again. > > > > > > I solved the issue by adding the immich Docker network ip address to the list of firewall rules > > Do you still remember which ip address you added? It turns out you should go to Container Manager and check all 4 instances of Immich and open the ports in your firewall rules. For me, they were 172.22.0.X.
OVERLORD commented 2026-02-05 05:27:45 +03:00
Author
Owner
Copy Link

@Georgie2323 commented on GitHub (Nov 21, 2024):

I have since deleted Immich - was so hard to keep it updated and will wait for a more mature version
From memory for me it was 10.xx.x.x.x

@Georgie2323 commented on GitHub (Nov 21, 2024): I have since deleted Immich - was so hard to keep it updated and will wait for a more mature version From memory for me it was 10.xx.x.x.x
OVERLORD commented 2026-02-05 05:27:48 +03:00
Author
Owner
Copy Link

@fluentnumbers commented on GitHub (Nov 21, 2024):

still experience this issue. When I switch off the firewall on my synology, the connection goes through, but swithing firewall back breaks it again.

I solved the issue by adding the immich Docker network ip address to the list of firewall rules

Do you still remember which ip address you added?

As said above, open the container manager-networks-immich_default and see the Gateway address. Then go to settings-Firewall and add a rule
image

@fluentnumbers commented on GitHub (Nov 21, 2024): > > > still experience this issue. When I switch off the firewall on my synology, the connection goes through, but swithing firewall back breaks it again. > > > > > > I solved the issue by adding the immich Docker network ip address to the list of firewall rules > > Do you still remember which ip address you added? As said above, open the container manager-networks-immich_default and see the Gateway address. Then go to settings-Firewall and add a rule ![image](https://github.com/user-attachments/assets/2fcfffa7-cb64-40cd-917e-54b612adcacb)
OVERLORD commented 2026-02-05 05:27:57 +03:00
Author
Owner
Copy Link

@PaulEins commented on GitHub (Jan 25, 2025):

Hi, i found you. I Have the 920+ too and it works perfekt. i Make clean isntall on my ssd and its very fast und grate.
i use the instalation from marius.
https://mariushosting.com/how-to-install-immich-on-your-synology-nas/

maybe, i help you, i wish you the best.

@PaulEins commented on GitHub (Jan 25, 2025): Hi, i found you. I Have the 920+ too and it works perfekt. i Make clean isntall on my ssd and its very fast und grate. i use the instalation from marius. https://mariushosting.com/how-to-install-immich-on-your-synology-nas/ maybe, i help you, i wish you the best.
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#2170
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?