consensus node not starting properly

[danlin85]

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

With the latest release i noticed that my images weren‘t syncing.
The logs showed that the consensus node didn‘t start.

The root cause was a malformed command entry in the Docker Compose configuration for any-sync-consensusnode, where the container tried to execute:

/bin/sh -c '[/bin/any-sync-consensusnode, -c, /etc/any-sync-consensusnode/config.yml]'

This string was incorrectly interpreted as a literal shell command instead of a proper exec‑style array, causing the container to fail with not found and immediately restart. As a result, the consensus node did not start reliably, which disrupted full synchronization (especially for assets like images), even though basic object sync appeared to work.
The issue was resolved by ensuring the command is set as a clean YAML list:

command: ["any-sync-consensusnode", "-c", "/etc/any-sync-consensusnode/config.yml"]

This prevents the shell wrapper and allows the binary to start directly, fixing the restart loop and restoring complete synchronization, including images.

Expected Behavior

As posted before

Steps To Reproduce

As posted before.

Environment

Proxmox LXC with latest Docker

Anything else?

No response