jeena/fxsync-docker
1
0
Fork 0
Code Issues 1 Pull requests Projects Packages Wiki Activity Actions

Thank you / a note about usability with recent versions. #1

New issue
Open
opened 2025-08-20 06:13:28 +00:00 by kivikakk · 1 comment
kivikakk commented 2025-08-20 06:13:28 +00:00
Copy link

Hi there! I found this repository really helpful while migrating my syncstorage-rs instance from one deployed with a NixOS module into Kubernetes.

Unfortunately, I ran into issues — it turns out that more recent versions of the image on Docker hub only support Spanner, and not MySQL. Indeed, I've just looked into it now that I got everything working, and it appears that they started feature-flagging support as of 0.14.0, allowing for only one of the two in a build, and (presumably all) the builds on Docker Hub made since then use the default feature, Spanner. The instance I migrated was on 0.18.2 previously and I didn't want to try rolling it back that far.

So, unless users stick with the version you've used in your docker-compose.yaml (0.13.6), they'll have to do as I did and build their own image to use! It's not too hard, thankfully: docker build . --build-arg DATABASE_BACKEND=mysql in a fresh clone will produce a correctly working image.

Thank you again!

Hi there! I found this repository really helpful while migrating my `syncstorage-rs` instance from one deployed with a NixOS module into Kubernetes. Unfortunately, I ran into issues — it turns out that more recent versions of the image on Docker hub _only_ support Spanner, and not MySQL. Indeed, I've just looked into it now that I got everything working, and it appears that they started feature-flagging support as of 0.14.0, allowing for only one of the two in a build, and (presumably all) the builds on Docker Hub made since then use the default feature, Spanner. The instance I migrated was on 0.18.2 previously and I didn't want to try rolling it back that far. So, unless users stick with the version you've used in your `docker-compose.yaml` (0.13.6), they'll have to do as I did and build their own image to use! It's not too hard, thankfully: `docker build . --build-arg DATABASE_BACKEND=mysql` in a fresh clone will produce a correctly working image. Thank you again!
jeena commented 2025-08-26 12:33:41 +00:00
Owner
Copy link

So does it mean that if instead of using image: mozilla/syncstorage-rs:0.13.6 in the docker-compose.yaml I probably should add the syncstorage-rs repo as a git-submodule and then do the build step in the docker-compose.yaml and then it would work?

So does it mean that if instead of using image: mozilla/syncstorage-rs:0.13.6 in the docker-compose.yaml I probably should add the syncstorage-rs repo as a git-submodule and then do the build step in the docker-compose.yaml and then it would work?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: jeena/fxsync-docker#1
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?