I have searched for any issue like this one and nothing that is suggested in the issues like this one has helped. I have created an automatic global update process, and it seems to run, but neither automatic nor manual "check" operations succeed, and because it's silent, there is no indication that it has failed. I have put the periphery on trace - nothing. I found this - the ONLY indication of failure - in the docker log for the core:
2026-08-29T06:30:29.474454Z WARN CheckStackForUpdate{operator="6732ffc1ba5d05b4ac240a95" stack="6733d8bcb5ee02cb413e590f"}:CheckStackForUpdateInner{stack="6733d8bcb5ee02cb413e590f"}: Failed to check for update | Stack: actual | Service: actual_server | Error: Decoded error message over Core-Periphery communication channel: unknown flag: --format
Usage: docker [OPTIONS] COMMAND [ARG...]
Run 'docker --help' for more information
This happens for every single stack, whether it is on the same machine as core or a different one. The periphery toml file has only one customisation and it's the public key required for the core to connect to it. Whether running the same or differing versions of core/periphery, the WARN remains (should probably be an error).
The only way I can check for updates rn is to pull every container and see if it takes time. All of these checks fail instantly.
I'd love to be able to see the periphery executing the commands to docker from the core but I just don't see anything happening.
The peripheries are all systemd services and the core runs in docker.
I have searched for any issue like this one and nothing that is suggested in the issues like this one has helped. I have created an automatic global update process, and it seems to run, but neither automatic nor manual "check" operations succeed, and because it's silent, there is no indication that it has failed. I have put the periphery on trace - nothing. I found this - the ONLY indication of failure - in the docker log for the core:
This happens for every single stack, whether it is on the same machine as core or a different one. The periphery
tomlfile has only one customisation and it's the public key required for the core to connect to it. Whether running the same or differing versions of core/periphery, the WARN remains (should probably be an error).The only way I can check for updates rn is to pull every container and see if it takes time. All of these checks fail instantly.
I'd love to be able to see the periphery executing the commands to docker from the core but I just don't see anything happening.
The peripheries are all systemd services and the core runs in docker.