#context canceled, manifest unknown

1 messages · Page 1 of 1 (latest)

shut sage
#

hi!
using rpi 4 , upgrading from 105.1 to 109.2 ( removed microservices lines)

[+] Running 2/2
 ✘ immich-machine-learning Error context canceled                                                                                                                                0.8s
 ✘ immich-server Error           manifest unknown                                                                                                                                0.8s
Error response from daemon: manifest unknown```


.env: 
```.env 

UPLOAD_LOCATION=/home/lumia/images
DB_DATA_LOCATION=./postgres

IMMICH_VERSION="1.109.2" #was previously 1.105.1

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

DB_USERNAME=mommyissues
DB_DATABASE_NAME=pics

docker-compose.yml:

services:
 immich-server:
   container_name: immich_server
   image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
   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-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```
limpid vaporBOT
#

:wave: Hey @shut sage,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich immich.

References

Checklist

  1. :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: I have read applicable release notes.
  3. :ballot_box_with_check: I have reviewed the FAQs for known issues.
  4. :ballot_box_with_check: I have reviewed Github for known issues.
  5. :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files, making sure to use code formatting.
  7. :ballot_box_with_check: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

shut sage
#

ènd of docker compose.yml : ``` redis:
image: registry.hub.docker.com/library/redis:6.2-alpine@sha256:84882e87b54734154586e5f8abd4dce69fe7311315e2fc6d67c29614c8de2672
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}
POSTGRES_INITDB_ARGS: '--data-checksums'
volumes:
- ${DB_DATA_LOCATION}:/var/lib/postgresql/data
restart: always
command: ["postgres", "-c" ,"shared_preload_libraries=vectors.so", "-c", 'search_path="$$user", public, vectors', "-c", "logging_collector=on", "-c", "max_wal_size=2GB", "-c", ">

volumes:
model-cache:


i did docker compose down then up ( applied remove orphan flag too ) and got these errors i have no idea what else to do now```
limpid vaporBOT
final wigeon
#

Can you try IMMICH_VERSION without quotes?

strong wharf
#

I would recommend that you check your old IMMICH_VERSION tag.I am sure it started with a v 😉

final wigeon
#

I feel like those might be messing it up

#

Ah, that's even better lol

shut sage
#

i'll check those brb

shut sage
#

"[+] Running 34/2 " i do not know how to count if this is correct lol

strong wharf
#

I'm not sure how to answer that

#

if your services work then it should be fine

shut sage
#

the pulling broke midway it retried that many times i think

strong wharf
#

maybe. try docker compose down and then bring it back up

shut sage
#

ope!

strong wharf
#

you need to setup websockets in the reverse proxy

shut sage
#

just time made it work

#

took a solid minute for websocket according to logs