Closed frewie closed 1 week ago
Not sure what the problem is as I never built for arm7 outside of GitHub actions. So, I re-enabled it and looks like it passed.
Please try pulling mandarons/icloud-drive:main
docker image until version 1.17.0
comes out.
Thank you very much! I pulled mandarons/icloud-drive:main but the problem remains. But I can now pull the image without problem. However, the process still exists with 0 or 139 on a QNAP TS-531X. Any ideas? I tried again both installation methods.
I am glad for any help. Best regards!
Please share the execution logs.
Thank you very much! I pulled mandarons/icloud-drive:main but the problem remains. But I can now pull the image without problem. However, the process still exists with 0 or 139 on a QNAP TS-531X. Any ideas? I tried again both installation methods.
I am glad for any help. Best regards!
Some QNAPs with armv7 was updated with page size 32K after that some containers that was created for page size 4K didnt work.
@magicse anyway I can tell
Thank you very much! I pulled mandarons/icloud-drive:main but the problem remains. But I can now pull the image without problem. However, the process still exists with 0 or 139 on a QNAP TS-531X. Any ideas? I tried again both installation methods. I am glad for any help. Best regards!
Some QNAPs with armv7 was updated with page size 32K after that some containers that was created for page size 4K didnt work.
@frewie do you think this is the root cause for your errors? @magicse any suggestions on how to resolve this? I don't have QNAP or any other ARM systems.
Unfortunately, this won't be fixed. I moved the base image to use linuxserver.io's alpine linux. It only supports amd64 and arm64.
Describe the bug
Great project! Everything works fine on my newer Apple Silicon mac. I tried to create a new docker image for arm v7 but without success. I tried installing the service on a QNAP NAS. The older version 1.12.0 can be deployed successfully on the NAS but only syncs 1 photo even when synching all albums is selected in the config file. Do you might know what could cause the issue here v1.12.0?
To Reproduce