Error Starting Seedsync - Due to old python version on remote

[J3tto]

While migrating to the fork, I'm getting and error.

Tried clearing out the /tmp folder which has write access and the new scripts are being created.
But fail to run and cause a boot loop.

Using latest docker build.

STDOUT
Starting SeedSync with UID=1000, GID=1000
STDOUT
Using existing group: seedsync (GID=1000)
STDOUT
Using existing user: seedsync (UID=1000)
STDOUT
Running as: seedsync:seedsync (UID=1000, GID=1000)
STDOUT
2026-03-24 20:44:11,157 - INFO - seedsync (MainProcess/MainThread) - Debug mode is disabled.
STDOUT
2026-03-24 20:44:11,158 - INFO - seedsync (MainProcess/MainThread) - Starting SeedSync
STDOUT
2026-03-24 20:44:11,158 - INFO - seedsync (MainProcess/MainThread) - Platform: x86_64
STDOUT
2026-03-24 20:44:12,324 - INFO - seedsync.WebApp (MainProcess/MainThread) - Html path set to: /app/html
STDOUT
2026-03-24 20:44:15,502 - INFO - RemoteScanner.RemoteScanner.Sshcp (RemoteScanner/RemoteScanner) - Detected remote shell: /bin/bash
STDOUT
2026-03-24 20:44:16,000 - INFO - RemoteScanner.RemoteScanner (RemoteScanner/RemoteScanner) - Skipping remote scanfs installation: already installed
STDERR
Process RemoteScanner:
STDERR
Traceback (most recent call last):
STDERR
File "/app/python/controller/scan/remote_scanner.py", line 90, in _run_scanfs_with_retry
STDERR
return self.__ssh.shell(
STDERR
^^^^^^^^^^^^^^^^^
STDERR
File "/app/python/ssh/sshcp.py", line 415, in shell
STDERR
return self.__run_command(command="ssh", flags=" ".join(flags), args=" ".join(args))
STDERR
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
STDERR
File "/app/python/ssh/sshcp.py", line 382, in __run_command
STDERR
raise SshcpError(out_before)
STDERR
ssh.sshcp.SshcpError: File "/tmp/scan_fs.py", line 11
STDERR
from __future__ import annotations
STDERR
^
STDERR
SyntaxError: future feature annotations is not defined

[nitrobass24]

Thanks for reporting this. The issue is that scan_fs.py (which runs on the remote seedbox) uses from __future__ import annotations, which requires Python 3.7+. Your remote server appears to have Python 3.6 or older.

This was introduced during the recent Ruff/Pyright modernization — the script previously used old-style type hints that worked on any Python 3 version.

Workaround: Check what Python version your seedbox has: python3 --version. If it's < 3.7, there's no workaround on the current release.

Fix: We'll remove the __future__ import and revert to Python 3.6-compatible type syntax in scan_fs.py. This is a quick fix.

What Python version does your seedbox report for python3 --version?

[J3tto]

Box is actually using 3.5

But the box allows me me to build and install a custom python, in my home (~/) but it looks like there is no way to override global path that's used on the remote. So the 3.5 version keeps getting used.

One idea might be having a way/override via config or ENV the remote python3 bin path to use on the remote?