syncstorage-rs-mysql-0.22.x images use Spanner backend (wrong build args in CI)

[my-flow]

Description

The syncstorage-rs-mysql-0.22.x images on ghcr.io appear to be compiled with the Spanner database backend despite the mysql tag, making them non-functional for MySQL/MariaDB deployments.

Symptoms

Starting a container from ghcr.io/porelli/firefox-sync:syncstorage-rs-mysql-0.22.x crashes immediately with:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: syncstorage_spanner::error::DbError::internal(...)'

The binary is looking for Spanner configuration/credentials even though the image tag says mysql.

Root Cause (suspected)

The syncstorage-rs Dockerfile requires two explicit build args to select the MySQL backend:

--build-arg SYNCSTORAGE_DATABASE_BACKEND=mysql
--build-arg TOKENSERVER_DATABASE_BACKEND=mysql

Without these, it defaults to the Spanner backend. The CI pipeline for the 0.22.x builds appears to be missing one or both of these args.

Affected versions

• syncstorage-rs-mysql-0.22.x (all builds checked)

Working versions

• syncstorage-rs-mysql-0.21.1 — correct MySQL backend, but missing the MariaDB FOR SHARE fix (Sync broken after syncstorage-rs-mysql-0.18.3-20250526T064429 #13)

[skazi0]

#20