PowerSync container missing in TrueNAS wger 2.6.0 app

[Phyxsius7]

Hi,

This is a followup on issue #5298 (@Etregin )

I have updated my TrueNAS wger app from 2.5 to 2.6.0 and noticed that the app starts the regular wger containers, but no separate PowerSync container is created.

Current TrueNAS containers:

ix-wger-server-1
ix-wger-nginx-1
ix-wger-worker-1
ix-wger-beat-1
ix-wger-postgres-1
ix-wger-redis-1

There is no container such as ix-wger-powersync-1, and I also do not see any container using the journeyapps/powersync-service image.

According to the official wger Docker Compose setup, PowerSync appears to be defined as a separate Compose service:
https://github.com/wger-project/docker/blob/master/docker-compose.yml

The dedicated PowerSync service definition uses its own image:
https://github.com/wger-project/docker/blob/master/services/powersync.yaml

Since a Docker Compose service normally results in a separate container, I would expect the TrueNAS app to create a separate PowerSync container as well, for example ix-wger-powersync-1 using the journeyapps/powersync-service image.

Without this container, the Android app 2.0.1 reports that the wger server is reachable, but the separate sync service is not responding.

Is it possible to see why PowerSync is not detected?

[stavros-k]

I'm not sure what this issue adds on top of the mentioned issue.
I think the linked issue makes it pretty clear that the container is not added yet.

[Phyxsius7]

I created this issue because @Etregin requested it.

I hope that closing this ticket does not mean that progress on the described issue will stop.

[Etregin]

@Phyxsius7 i think there was a misunderstanding , the issue mentioned is whats used to track this, there is a PR open and im currently working with @stavros-k to getting it clear

[Phyxsius7]

No problem. Now that you mentioned it, I better understand what your previous request implied.
My apologies for any inconvenience caused.