any-sync-consensusnode:v0.6.8 (prod) broken - wrong syntax for cmd

[tobiaskitsune]

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

When starting a fresh install with default settings by "make start" the container "any-sync-consensusnode" is not coming up and restarting continuously. The container logs show an error:

/bin/sh: 1: [/bin/any-sync-consensusnode,: not found

This indicates a syntax error in the container:

"Cmd": [
"/bin/sh",
"-c",
"[/bin/any-sync-consensusnode, -c, /etc/any-sync-consensusnode/config.yml]"
],

Expected Behavior

The container should start normally without error.

This can be enforced by overwriting the command in the docker.compose file by adding this code:

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

Steps To Reproduce

Under OpenSUSE Tumbleweed with Docker and Almalinux 10 with Docker

mkdir /var/opt/any-sync-dockercompose
cd /var/opt/any-sync-dockercompose
git clone https://github.com/anyproto/any-sync-dockercompose.git
make start

Environment

- OS: openSUSE and Almalinux
- Version: Tumbleweed / 10
- any-sync-consensusnode:v0.6.8 (prod)

Anything else?

No response

[zubi33]

I had the same probleme with any-sync-consensusnode and any-sync-filenode in latest version. I write the .env.override to prod:

ANY_SYNC_NODE_VERSION=prod
ANY_SYNC_FILENODE_VERSION=prod
ANY_SYNC_COORDINATOR_VERSION=prod
ANY_SYNC_CONSENSUSNODE_VERSION=prod
ANY_SYNC_TOOLS_VERSION=latest

Try to download the version 0.6.7:
docker pull ghcr.io/anyproto/any-sync-consensusnode:v0.6.7 && \\ndocker inspect ghcr.io/anyproto/any-sync-consensusnode:v0.6.7 | grep -A5 '"Cmd"'

After i fix the docker-compose.yml for any-sync-consensusnode :

any-sync-consensusnode:
    image: "ghcr.io/anyproto/any-sync-consensusnode:${ANY_SYNC_CONSENSUSNODE_VERSION}"
    command: ["/bin/any-sync-consensusnode", "-c", "/etc/any-sync-consensusnode/config.yml"]

This fix the problem.

[tobiaskitsune]

This fix the problem.

Your code as well my code above fix the problem. It is the same, just another syntax.

[sususu98]

Same issue confirmed. The root cause is in the upstream image — the Dockerfile in any-sync-consensusnode uses unquoted CMD entries, so Docker interprets it as shell form instead of exec form:

# What's in the v0.6.8 image:
CMD ["/bin/sh", "-c", "[/bin/any-sync-consensusnode, -c, /etc/any-sync-consensusnode/config.yml]"]

# What it should be:
CMD ["/bin/any-sync-consensusnode", "-c", "/etc/any-sync-consensusnode/config.yml"]

Upstream issue: anyproto/any-sync-consensusnode#91

Suggest adding the command override to docker-compose.yml as a workaround until the upstream image is fixed.

[mighty-sponge]

Hi! We had an issue with escaping single quotes in the build workflow and we've fixed it. Please re-pull your image ghcr.io/anyproto/any-sync-consensusnode:v0.6.8 and everything should work.

[automatedcolleague]

Same broken CMD in any-sync-coordinator:v0.9.0 and any-sync-filenode:v0.11.0 — only consensusnode was rebuilt after the workflow fix on Mar 30.

docker inspect --format '{{.Created}} {{.Config.Cmd}}':
consensusnode:v0.6.8  2026-03-30  [/bin/any-sync-consensusnode -c ...]     ✅
coordinator:v0.9.0    2026-03-19  [/bin/sh -c [/bin/any-sync-coordinator,  ❌
filenode:v0.11.0      2026-03-19  [/bin/sh -c [/bin/any-sync-filenode,     ❌

Could you rebuild these two images?

[mighty-sponge]

Hi! Done. Re-pull please.

[automatedcolleague]

Works great, thanks!