No matching tag to upgrade any-sync-dockercompose for new client desktop v 0.50.5

[Valink]

Have you read a contributing guide?

• I have read CONTRIBUTING.md
• I have searched the existing issues and didn't find any that were similar
• I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

Self host error : infinite sync after installing update v0.50.5 for Windows client

Expected Behavior

Sync

Steps To Reproduce

• use working installation with tag v6.3.0 and windows client 0.49.2
• update to windows client to 0.50.5
• error on sync

Environment

Client
- OS: Windows 11
- Version: 10.0.26100 Build 26100

Server
- Debian 11

Anything else?

Workarround : anyway to downgrade to 0.49.X without losing data ?

[Valink]

Workarround found : install 0.49.2 over current installation.
https://anytype-release.fra1.cdn.digitaloceanspaces.com/Anytype%20Setup%200.49.2.exe

[fb929]

can you show the images version?

docker ps --format '{{.ID}} {{.Image}}' | while read -r id image; do     image_id=$(docker inspect --format '{{.Image}}' "$id");     echo "Container: $id, Image: $image, Image ID: $image_id"; done

[GavinRest]

I also encountered the same problem, downgrading solved it

[fb929]

I think the issue here might be caused by old versions of the any-sync-* images, but I can say for sure only if you provide the output of the command above.
if that’s the case, updating the server versions via make update should help.

[ClaudiaFang]

Thanks to @fb929 suggestion. I upgrade server side any-sync-* image to newest version via update .env. It is worked with v0.50.5 MacOS and iOS 0.40.1 client.

ANY_SYNC_NODE_VERSION=v0.9.2
ANY_SYNC_FILENODE_VERSION=v0.9.2
ANY_SYNC_COORDINATOR_VERSION=v0.7.3
ANY_SYNC_CONSENSUSNODE_VERSION=v0.4.1

[fb929]

updating versions manually isn't necessary - it happens automatically when starting via make

[Valink]

can you show the images version?

docker ps --format '{{.ID}} {{.Image}}' | while read -r id image; do     image_id=$(docker inspect --format '{{.Image}}' "$id");     echo "Container: $id, Image: $image, Image ID: $image_id"; done

Sorry for the delay, I didn't receive the Github notification

Container: 285c8db21679, Image: ghcr.io/anyproto/any-sync-tools:latest, Image ID: sha256:59a971222505c3f2853c263e1ffa659c319ece448a982b03837cf9eb90fd40dd
Container: 4b52df13fe5a, Image: ghcr.io/anyproto/any-sync-node:v0.7.6, Image ID: sha256:1d45c6bf729976301f36dfb6be453afb91665b4b337b4ad6290c6fd4efe93037
Container: 286b2f77b11e, Image: ghcr.io/anyproto/any-sync-consensusnode:v0.2.3, Image ID: sha256:23a4f7dc58b0acc1983bc1d72400c666a7ec26e59c4c9c95a004c04074798894
Container: 6e005d1319dd, Image: ghcr.io/anyproto/any-sync-filenode:v0.8.12, Image ID: sha256:dc9c0736916246c36ab7dea4960fe819ea52449d0e93e62e9aec988b1655d4be
Container: cf52f0a57a85, Image: ghcr.io/anyproto/any-sync-node:v0.7.6, Image ID: sha256:1d45c6bf729976301f36dfb6be453afb91665b4b337b4ad6290c6fd4efe93037
Container: a6e817b1eda9, Image: ghcr.io/anyproto/any-sync-node:v0.7.6, Image ID: sha256:1d45c6bf729976301f36dfb6be453afb91665b4b337b4ad6290c6fd4efe93037
Container: 16fcf335ff32, Image: ghcr.io/anyproto/any-sync-coordinator:v0.5.1, Image ID: sha256:9615a589654a349f8b774f0c56122bba5837d1a2f9e89c593f1ec0a249f884e1
Container: 5d2576dfee05, Image: redis/redis-stack-server:7.2.0-v6, Image ID: sha256:ebee26a6f06392afaa518dd7fb4b8753e1f0400889123d144928aaeed3d12dd4
Container: 53523ff0d784, Image: mongo:7.0.2, Image ID: sha256:ee3b4d1239f12b094c4936dd08a2fbc227300beaf784c46c509e2f1ac5e6d879
Container: bcf9c35ff069, Image: minio/minio:RELEASE.2024-07-04T14-25-45Z, Image ID: sha256:a9368d642903a117fc2ba7637e09737ea295a499182e5a56178e8081a89e3fe0
Container: db756ad41c12, Image: sintan1729/chhoto-url:latest, Image ID: sha256:d60e6b11ba8562730055b01e3b9325c97e3725ef907ab970e250a79915bf9943
Container: 390318d711c8, Image: mattermost/focalboard, Image ID: sha256:58f6f9f2684a6f8780857909db2a4d96093f792ad8b612722d3b6f7ca2512f50

After redoing the upgrade with the last available tag 6.3.0 :

git fetch -pP
git checkout v6.3.0
make generate_env
make restart

Container: 5f05716c8287, Image: ghcr.io/anyproto/any-sync-tools:latest, Image ID: sha256:256c933a3d72d72b60b71d02994bdd82137f2c775b094c23d0f3d61d16faa9fa
Container: 427fb067e283, Image: ghcr.io/anyproto/any-sync-node:v0.9.3, Image ID: sha256:88dc732496cad819163ca9c737bd7796ed3b2f98988f748524b19dd2881201a1
Container: c816e444dfe5, Image: ghcr.io/anyproto/any-sync-consensusnode:v0.4.2, Image ID: sha256:a724fc317d8148ff48890753a6e9014f09d2e8d85385888220833a9971034269
Container: a1d0789f27e9, Image: ghcr.io/anyproto/any-sync-filenode:v0.9.2, Image ID: sha256:549d0eca9223aa33a623dc2bed436ee145a93553a34d6081f39f7cff433b0128
Container: d8c27483ae97, Image: ghcr.io/anyproto/any-sync-node:v0.9.3, Image ID: sha256:88dc732496cad819163ca9c737bd7796ed3b2f98988f748524b19dd2881201a1
Container: 3c8fbee57154, Image: ghcr.io/anyproto/any-sync-node:v0.9.3, Image ID: sha256:88dc732496cad819163ca9c737bd7796ed3b2f98988f748524b19dd2881201a1
Container: 11aad4d4aef2, Image: ghcr.io/anyproto/any-sync-coordinator:v0.7.3, Image ID: sha256:2b511fbb08209fce30f5441f3b476e622035c496361e4ea59a93da2ae8511dd8
Container: 65189b0c2f1a, Image: mongo:7.0.2, Image ID: sha256:ee3b4d1239f12b094c4936dd08a2fbc227300beaf784c46c509e2f1ac5e6d879
Container: 8111e455bd26, Image: redis/redis-stack-server:7.2.0-v6, Image ID: sha256:ebee26a6f06392afaa518dd7fb4b8753e1f0400889123d144928aaeed3d12dd4
Container: 816fb36f02bb, Image: minio/minio:RELEASE.2024-07-04T14-25-45Z, Image ID: sha256:a9368d642903a117fc2ba7637e09737ea295a499182e5a56178e8081a89e3fe0
Container: db756ad41c12, Image: sintan1729/chhoto-url:latest, Image ID: sha256:d60e6b11ba8562730055b01e3b9325c97e3725ef907ab970e250a79915bf9943
Container: 390318d711c8, Image: mattermost/focalboard, Image ID: sha256:58f6f9f2684a6f8780857909db2a4d96093f792ad8b612722d3b6f7ca2512f50

This is now working with 0.50+ thank you !

From this step, doing make upadte did not change more images version.
I guess the upgrade does a make update somehow...
In the future, do we need to stick to the tag v6.3.0 or do we need to switch over a production branch ?

[fb929]

version updates of any-sync-* daemons occur during make start (and any commands that invoke start, such as restart, update, etc.).
accordingly, to update the server versions, it’s enough to run make restart or make update (in fact, these commands don’t differ much).

I recommend always keeping the any-sync-dockercompose repository on the "latest release" - https://github.com/anyproto/any-sync-dockercompose/releases
we always publish a new release whenever we make updates to the self-host code required for the operation of new server versions.

[freakadings]

I got the same Problem on linux mint with the latest client version
I tried everything mentioned here,
docker compose pull
docker compose down
docker compose up -d

tried to set the versions manually within the .env.override
tried to checkout to the latest branch ( which set git to detached head state)

And every command mentioned within the makefile (my server has no "make")
but only downgrading the client helped.

(edit: Forgot to mention that the android-app is out of sync too and at some point even the connection-indicator-dot-thingy within the linux client disappeared completely)

[fb929]

And every command mentioned within the makefile (my server has no "make") but only downgrading the client helped.

if you don't have the make utility, use this instruction.
each time before running docker compose up, you need to run the "Generate config" commands.

and show which versions you ended up with:

docker ps --format '{{.ID}} {{.Image}}' | while read -r id image; do     image_id=$(docker inspect --format '{{.Image}}' "$id");     echo "Container: $id, Image: $image, Image ID: $image_id"; done

[freakadings]

That link was very useful!
I couldn't find another "how to update" page.
After executing:
docker buildx build --tag generateconfig-env --file Dockerfile-generateconfig-env . docker run --rm --volume ${PWD}/:/code/ generateconfig-env docker compose up -d

They are finale up to date (were all on other versions before)
Container: b04ea90b6258, Image: ghcr.io/anyproto/any-sync-tools:latest, Image ID: sha256:256c933a3d72d72b60b71d02994bdd82137f2c775b094c23d0f3d61d16faa9fa Container: 4f42daa5830c, Image: ghcr.io/anyproto/any-sync-node:v0.9.3, Image ID: sha256:88dc732496cad819163ca9c737bd7796ed3b2f98988f748524b19dd2881201a1 Container: a91896919afc, Image: ghcr.io/anyproto/any-sync-node:v0.9.3, Image ID: sha256:88dc732496cad819163ca9c737bd7796ed3b2f98988f748524b19dd2881201a1 Container: 310b7fd74468, Image: ghcr.io/anyproto/any-sync-filenode:v0.9.2, Image ID: sha256:549d0eca9223aa33a623dc2bed436ee145a93553a34d6081f39f7cff433b0128 Container: d9e21ddded66, Image: ghcr.io/anyproto/any-sync-consensusnode:v0.4.2, Image ID: sha256:a724fc317d8148ff48890753a6e9014f09d2e8d85385888220833a9971034269 Container: 95b16b99042f, Image: ghcr.io/anyproto/any-sync-node:v0.9.3, Image ID: sha256:88dc732496cad819163ca9c737bd7796ed3b2f98988f748524b19dd2881201a1 Container: 05bb458aa015, Image: ghcr.io/anyproto/any-sync-coordinator:v0.7.3, Image ID: sha256:2b511fbb08209fce30f5441f3b476e622035c496361e4ea59a93da2ae8511dd8

Thank you very much!