You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point, arm64 builds may be able to be turned on for linux/arm64. RPi4 8GB should be able to handle TaleCaster duties assuming NAS, but will need the config stored on something besides eMMC or SD. If stored on these, the configuration stores will brick the module in a matter of weeks at the longest.
Linux/arm64 restrictions will be documented in the Wiki for now.
The text was updated successfully, but these errors were encountered:
On hold due to Jackett not producing musl CLR currently. Working with the Jackett team to resolve the musl absence, which should restore arm64 capability.
This has largely been solved by moving to Prowlarr (which is much more actively maintained,) but I need to find a better way for workflows to build x64 and arm64 separately at minimum. Preferably re-minimize builds on pull/merge, but the dependency chaining (tc_docker -> *) causes a problem there.
At this point, arm64 builds may be able to be turned on for linux/arm64. RPi4 8GB should be able to handle TaleCaster duties assuming NAS, but will need the config stored on something besides eMMC or SD. If stored on these, the configuration stores will brick the module in a matter of weeks at the longest.
Linux/arm64 restrictions will be documented in the Wiki for now.
The text was updated successfully, but these errors were encountered: