HW transcoding not working for Alpine (-noml) and Synology Intel #207
Comments
|
Right, I didn't test if the noml version is compatible with hardware transoding and I wouldn't be surprised if it is not. As for #168, it addresses a permission issue. If you'd like to test it, follow these steps: create a new Then add the new volume to your immich container volumes:
- ${CONFIG}/immich:/config
- ${MEDIA}/photos:/photos
- ${CONFIG}/custom-cont-init.d:/custom-cont-init.d:roIf this does not work, this is definetly an alpine issue |
|
Thanks. Looks like something different is happening, at least! Looks like it fails hw transcoding with a device creation / IO error, and then falls back to software and succeeds. i'm a bit of a linux dumbass so i'm hoping these permissions are right: (the docker user is what is assigned to the PGID/PUID of the immich container) |
|
Can you pull the image again. |
|
thanks! I have tried after a pull and get a lot of this error now : I am using the docker-compose in my first post. So it's using It seemed to work before, at least! |
|
Can you try to delete the redis folder in |
|
Tried that, and still getting similar errors, but there's a few strange ones earlier that may be releated: |
|
Oh damn are you using the postgres docker mod ? I don't understand why you have such errors with redis. @hydazz any ideas ? |
|
the postgres docker mod continued to work on alpine, as their package support is more legacy, but its now based on debian and there is no postgres 14, I presume that its trying to install PG14, failing and skipping installing redis |
|
I mean for this error |
|
redis is not installed, as postgres fails to install |
|
Sorry for the delay. I have added postgres to my -noml compose, rather than use the docker mod. i am getting a loop of: Note I am still using postgres 14, as using postgres 15 as per the latest readme gives me a compatibility error with my previously built postgres 14 database. i could just delete this but i presume that will cause problems with my current immich installation(?). anyway, postgres (14) seems to start up ok: also note that I'm not using external db port 5432 as synology OS already uses that for something, so I have forwarded from 6543 (I think). |
|
You need to change |
|
thanks, though I'm still struggling! latest compose: I have changed or 5432: (I guess they both log port 5432 as 6543:5432 just forwards to 5432 within the container) i then tried using the internal IP of this box: 192:168:1.4 as DB_HOSTNAME and it seems to connect but errors: |
|
hello dit you still struggling ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, Getting this sort of thing in the logs:
This is with a Synology 423+ NAS which has Intel J4124, which has quicksync.
Here's my docker compose:
(I am not sure if
privileged: trueis needed, but is used in my Plex service, where hardware transcoding via- /dev/dri:/dev/driworks fine)I have not tried the regular image, or indeed the immich vanilla docker compose, but I was under the impression that hw transcoding might work in alpine as per #148 (comment)
These errors look like a driver type issue, so I wonder if maybe the above PR or #168 are not available/possible in the noml image?
The text was updated successfully, but these errors were encountered: