Skyler Mäntysaari
Skyler Mäntysaari
I have also noticed this issue on Android. 
It can also happen that the copy was successful but the move from the copy to the destination pvc is not..
I'm noticing that the `quay.io/backube/volsync:0.8.0` image is not arm64 compatible. `exec /mover-restic/entry.sh: exec format error` Aka `quay.io/backube/volsync@sha256:b0969dce78b900412303153f0761b2233204164572eff1aeebf31707db7e20db`
> Its done. > > Tags "latest" and "main" is the main branch. Tag "0.8.0" is release-0.8 branch Seems like not quite when trying to use it for restic. `exec...
amd64 and arm64 supported: `registry.samipsolutions.fi/library/volsync:0.8.0`
Hmm, I wonder if there actually is some MOV's that are actually non-quicktime videos according to exiftool.. I think we should be accepting video/mov as well.
Support for MOV should be implemented as of #2045, eg included in Immich version 1.52.0.
None of the images are built for arm64.
> see https://github.com/goharbor/harbor-arm Rather, see https://github.com/octohelm/harbor for actual images as the harbor-arm repository hasn't had a commit in age, eg latest one is a year ago at least and there...
Ah, so that's why I did not see 4K listed at all... That's annoying..