Lemmy Support @lemmy.ml minnix @lemux.minnix.dev 3w ago

Need clarification on pictrs update to 0.5 for 19.4 - Docker Compose

Anyone care to share their docker compose file for the upgrade? Or at least the pictrs portion? I've upgraded and migrated postgres to 16, but am having issues with the pictrs part.

7 comments

Set image tag in pictrs section to 0.5 and change to the new ENV format described in the docs of pictrs. At last start only the pictrs container docker compose up -d pictrs

Here is my example in the new formaz. Be aware it is just an example ☝🏻

pictrs: image: asonix/pictrs:0.5 container_name: lemmy-pictrs # this needs to match the pictrs url in lemmy.hjson hostname: pictrs # we can set options to pictrs like this, here we set max. image size and forced format for conversion # entrypoint: /sbin/tini -- /usr/local/bin/pict-rs -p /mnt -m 4 --image-format webp environment: - PICTRS_OPENTELEMETRY_URL=http://otel:4137 - PICTRS__SERVER__API_KEY=redacted - RUST_LOG=info - RUST_BACKTRACE=full - PICTRS__MEDIA__VIDEO__VIDEO_CODEC=vp9 - PICTRS__MEDIA__ANIMATION__MAX_WIDTH=256 - PICTRS__MEDIA__ANIMATION__MAX_HEIGHT=256 - PICTRS__MEDIA__ANIMATION__MAX_AREA=65536 - PICTRS__MEDIA__ANIMATION__MAX_FRAME_COUNT=400 user: 991:991 volumes: - ./volumes/pictrs:/mnt:Z restart: always logging: *default-logging deploy: resources: limits: memory: 690m
- Mind you that PICTRS__API_KEY is the wrong variable, and should be PICTRS__SERVER__API_KEY. I've noticed it when Lemmy Thumbnail Cleaner complained about the api key being incorrect. Follow the repo page and check if your variables are correct.
  
  This one isn't mentioned here https://git.asonix.dog/asonix/pict-rs#0-4-to-0-5-migration-guide
  
  PICTRS__SERVER__API_KEY
  
  Good catch.
  
  Thanks, I edited the compose file. I overlooked this one. The docker-compose example for Lemmy on Github still has the old ENV. Maybe this one should be edited too
- This is the part of the new compose file that I don't understand:
  
  PICTRS__OLD_REPO__PATH=/mnt/sled-repo PICTRS__REPO__TYPE=postgres PICTRS__REPO__URL=postgres://user:password@host:5432/db
  
  When I try to add it, pictrs complains about not being able to connect to postgres, even though the credentials are correct and I've already run the postgres migration script. Did you not do this part when you upgraded?
  
  No I just replaced the image tag. Pictrs will do the upgrade itself.
  
  This is for making the pictrs backend on postgres and to migrate it to postgres. Though not documented with Lemmy it works and I am running it that way on my instance. It allows you to load balance and have high availability of pictrs service.

7 comments