-
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.
The bugHello, I have been running immich in portainer for over a year now, and applying updates as they have been released. I'm currently running 1.127.0, and its solid. I have tried to update to 1.128.0 and 1.129.0, and every time the immich_server service keeps flapping. It starts and stops. I have to revert my snapshot each time I try to update. I'm not docker expert, and kind of stuck to why the service is flapping. Any help would be appreciated. The OS that Immich Server is running onUbuntu 22.04.5 Version of Immich Server1.127.0 Version of Immich Mobile App1.129.0 Platform with the issue
Your docker-compose.yml content#
# 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}
#Old Command command: ['start.sh', 'immich']
volumes:
- ${UPLOAD_LOCATION}:/usr/src/app/upload
- ${EXTERNAL_PATH}:/usr/src/app/external
- /etc/localtime:/etc/localtime:ro
env_file:
- stack.env
ports:
- 2283:2283
depends_on:
- redis
- database
restart: always
#Microservices module no longer needed
# 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
# - ${EXTERNAL_PATH}:/usr/src/app/external
# - /etc/localtime:/etc/localtime:ro
# env_file:
# - stack.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:
- stack.env
restart: always
redis:
container_name: immich_redis
image: registry.hub.docker.com/library/redis:6.2-alpine@sha256:51d6c56749a4243096327e3fb964a48ed92254357108449cb6e23999c37773c5
restart: always
database:
container_name: immich_postgres
image: registry.hub.docker.com/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
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 contentUPLOAD_LOCATION=./library
IMMICH_VERSION=release
DB_PASSWORD=default values
DB_HOSTNAME=immich_postgres
DB_USERNAME=default values
DB_DATABASE_NAME=immich
REDIS_HOSTNAME=immich_redisReproduction steps1.Log into portainer, re-pull image to update Relevant log outputAdditional informationThis is currently running in vmware 8.0U3. 4 vCPU 8Gig Ram. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 10 replies
-
|
Please share the logs. There must be some error causing Immich to die. |
Beta Was this translation helpful? Give feedback.
-
|
So it looks like i have an incomplete scan. i'm assuming something is corrupt and causing the instability? Let me know your thoughts. Thanks!! } drewsky@drewsky-docker:~$ |
Beta Was this translation helpful? Give feedback.
-
|
My appologies. The logs we would need are these on the immich_server service restarting. I just re-ran the update to bring back the issue and grabbed the proper logs. drewsky@drewsky-docker:~$ docker logs db1fa6676ab4 |
Beta Was this translation helpful? Give feedback.
-
This is the actual issue. Ignore the stuff at the start |
Beta Was this translation helpful? Give feedback.
-
|
I saw that in the logs. How do I go about resolving this issue? If i go to that file location, I can open the file but i can't delete it. Is there a way to re-create this file? |
Beta Was this translation helpful? Give feedback.
-
That indicates you have some permission issues going on. Fix those |
Beta Was this translation helpful? Give feedback.
-
|
Hi Team, Configuration |
Beta Was this translation helpful? Give feedback.
-
|
@adikpetoaleton please create your own thread. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
-
|
I spoke too soon. Everything is running as it should. Most of the older images are now showing error on loading image. Any Ideas? |
Beta Was this translation helpful? Give feedback.
-
|
Please share your compose and .env as they are right now. It sounds to me like some things are set wrong and you might risk losing data if you keep running with that. |
Beta Was this translation helpful? Give feedback.
-
|
I ended up reverting my snapshot on my VM. My compose, and .env are back to as they were above. And the funny thing is that, if i put back my compose, and .env files back to where they were when i had it working with no thumbnails. My service starts to flap again. So i think something underlying is going on. What is the best way to get the logs so i can upload them so we can review them. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Hello,
It happened not to be a permissions issue. Under environmental variables,
for UPLOAD_LOCATION=./library, Is how it has been set since i set this up
over a year ago. It was saying that the file didn't exist. When you
deploy with portainer it creates a data path where everything is dumped
in. I'm assuming something with the last two updates, it doesn't like that
path or does some kind of check. I had to update the
UPLOAD_LOCATION=/data/compose/1/library, to the actual path, and everything
started working right away. I'm going to leave my snap for a few days to
make sure it stays stable, but I think that was the issue.
I want to thank everyone for their help and input. I learned a lot more on
how this works, and how everything talks.
Thanks again
…On Fri, Mar 7, 2025 at 4:06 PM Daniel Dietzler ***@***.***> wrote:
I can open the file but I can't delete it
That indicates you have some permission issues going on. Fix those
—
Reply to this email directly, view it on GitHub
<#16626 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AP7J225Y2A4ZODLT63UGITL2TIC5HAVCNFSM6AAAAABYQ36PEWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBTGA4DIOA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Andrew Lippelman
|
Beta Was this translation helpful? Give feedback.
Hello,
I was able to fumble through and get this issue resolved. The main thing I had to do, was to update my .yml file. Instead of replacing the entire existing one. I just updated the services modules in my older file to the latest settings. I had to leave the volume values alone. And for the environment values, I did add the DB_DATA_LOCATION=pgdata:/var/lib/postgresql/data. If I didn't add the pgdata to the path, it created a new instance of immich. I don't fully understand why, but its working as it should, updates are working, and everything is running great. I hope this makes sense, and helps anyone else seeing this issue.