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

[BUG] Unable to update through Portainer to v1.43.0/v1.43.1 #636

New Issue
Closed
opened 2026-02-04 21:36:08 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2026-02-04 21:36:08 +03:00
Owner
Copy Link

Originally created by @pig-cop on GitHub (Jan 30, 2023).

Until now I always updated flawlessly through Portainer simply updating the stack after changing the TAG values in the docker-compose configuration.
Since v1.43.0 I get the attached error.
I can still downgrade without any issues to the release tag or any of the dev tags before v1.43.0.

immich_update_error

Originally created by @pig-cop on GitHub (Jan 30, 2023). Until now I always updated flawlessly through Portainer simply updating the stack after changing the TAG values in the docker-compose configuration. Since v1.43.0 I get the attached error. I can still downgrade without any issues to the release tag or any of the dev tags before v1.43.0. ![immich_update_error](https://user-images.githubusercontent.com/1793444/215502490-4c573c85-fdae-465b-bbbb-8a2045f95e12.jpg)
OVERLORD commented 2026-02-04 21:36:17 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jan 30, 2023):

Can you provide your docker-compose content?

@alextran1502 commented on GitHub (Jan 30, 2023): Can you provide your docker-compose content?
OVERLORD commented 2026-02-04 21:36:20 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Jan 30, 2023):

I believe there is a max amount of time portainer waits before showing an error and reporting the deployment failed, but that is often unrelated to the actual deployment. I'd just try again, the new images should now be available locally.

@jrasm91 commented on GitHub (Jan 30, 2023): I believe there is a max amount of time portainer waits before showing an error and reporting the deployment failed, but that is often unrelated to the actual deployment. I'd just try again, the new images should now be available locally.
OVERLORD commented 2026-02-04 21:36:27 +03:00
Author
Owner
Copy Link

@pig-cop commented on GitHub (Jan 30, 2023):

Can you provide your docker-compose content?

Sure, here you go:

version: "3.8"

services:
  immich-server:
    container_name: immich_server
    image: altran1502/immich-server:${TAG}
    entrypoint: ["/bin/sh", "./start-server.sh"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - stack.env
    environment:
      - NODE_ENV=production
    depends_on:
      - redis
      - database
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: altran1502/immich-server:${TAG}
    entrypoint: ["/bin/sh", "./start-microservices.sh"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - stack.env
    environment:
      - NODE_ENV=production
    depends_on:
      - redis
      - database
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: altran1502/immich-machine-learning:${TAG}
    entrypoint: ["/bin/sh", "./entrypoint.sh"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - stack.env
    environment:
      - NODE_ENV=production
    depends_on:
      - database
    restart: always

  immich-web:
    container_name: immich_web
    image: altran1502/immich-web:${TAG}
    entrypoint: ["/bin/sh", "./entrypoint.sh"]
    env_file:
      - stack.env
    environment:
      # Rename these values for svelte public interface
      - PUBLIC_IMMICH_SERVER_URL=${IMMICH_SERVER_URL}
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2
    restart: always

  database:
    container_name: immich_postgres
    image: postgres:14
    env_file:
      - stack.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: altran1502/immich-proxy:${TAG}
    environment:
      # Make sure these values get passed through from the env file
      - IMMICH_SERVER_URL
      - IMMICH_WEB_URL
    ports:
      - 2283:8080
    logging:
      driver: none
    depends_on:
      - immich-server
    restart: always

volumes:
  pgdata:

I have an environment variable for the tags.

I believe there is a max amount of time portainer waits before showing an error and reporting the deployment failed, but that is often unrelated to the actual deployment. I'd just try again, the new images should now be available locally.

I don't know if that's the issue, I have already tried many times.

@pig-cop commented on GitHub (Jan 30, 2023): > Can you provide your docker-compose content? Sure, here you go: ``` version: "3.8" services: immich-server: container_name: immich_server image: altran1502/immich-server:${TAG} entrypoint: ["/bin/sh", "./start-server.sh"] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - stack.env environment: - NODE_ENV=production depends_on: - redis - database restart: always immich-microservices: container_name: immich_microservices image: altran1502/immich-server:${TAG} entrypoint: ["/bin/sh", "./start-microservices.sh"] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - stack.env environment: - NODE_ENV=production depends_on: - redis - database restart: always immich-machine-learning: container_name: immich_machine_learning image: altran1502/immich-machine-learning:${TAG} entrypoint: ["/bin/sh", "./entrypoint.sh"] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - stack.env environment: - NODE_ENV=production depends_on: - database restart: always immich-web: container_name: immich_web image: altran1502/immich-web:${TAG} entrypoint: ["/bin/sh", "./entrypoint.sh"] env_file: - stack.env environment: # Rename these values for svelte public interface - PUBLIC_IMMICH_SERVER_URL=${IMMICH_SERVER_URL} restart: always redis: container_name: immich_redis image: redis:6.2 restart: always database: container_name: immich_postgres image: postgres:14 env_file: - stack.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: altran1502/immich-proxy:${TAG} environment: # Make sure these values get passed through from the env file - IMMICH_SERVER_URL - IMMICH_WEB_URL ports: - 2283:8080 logging: driver: none depends_on: - immich-server restart: always volumes: pgdata: ``` I have an environment variable for the tags. > I believe there is a max amount of time portainer waits before showing an error and reporting the deployment failed, but that is often unrelated to the actual deployment. I'd just try again, the new images should now be available locally. I don't know if that's the issue, I have already tried many times.
OVERLORD commented 2026-02-04 21:36:30 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jan 30, 2023):

I don't see anything abnormal here. I just checked the images on DockerHub and I can see v1.43.1 available for all images.

Maybe restart Portainer?

@alextran1502 commented on GitHub (Jan 30, 2023): I don't see anything abnormal here. I just checked the images on DockerHub and I can see [v1.43.1](https://hub.docker.com/layers/altran1502/immich-machine-learning/v1.43.1/images/sha256-5f89ffafe4287777307c5e8f9592601543a291d72a805c6eac0ff89079f7591d?context=repo) available for all images. Maybe restart Portainer?
OVERLORD commented 2026-02-04 21:36:34 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Jan 30, 2023):

What tag are you using?

@jrasm91 commented on GitHub (Jan 30, 2023): What tag are you using?
OVERLORD commented 2026-02-04 21:36:36 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Jan 30, 2023):

It's worth point out the tag structure changed. It was v1.42.0_65-dev, but it's now v1.43.1.

@jrasm91 commented on GitHub (Jan 30, 2023): It's worth point out the tag structure changed. It was `v1.42.0_65-dev`, but it's now `v1.43.1`.
OVERLORD commented 2026-02-04 21:36:38 +03:00
Author
Owner
Copy Link

@pig-cop commented on GitHub (Jan 30, 2023):

My bad sorry, I double checked the locally available images and found out that I had some images of a previous failed installation.
I think yesterday at some point I closed accidentally the browser tab before the stack was deployed.

Cleared the failed images and updated successfully using tag v1.43.1, thanks for making me realize my mistake!

@pig-cop commented on GitHub (Jan 30, 2023): My bad sorry, I double checked the locally available images and found out that I had some images of a previous failed installation. I think yesterday at some point I closed accidentally the browser tab before the stack was deployed. Cleared the failed images and updated successfully using tag ```v1.43.1```, thanks for making me realize my mistake!
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#636
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?