What happened?
I started with nebular-sync and used the compose from the README.
When starting that compose it results in error 139.
admin@diskstation:/volume1/docker/nebular-sync$ sudo docker-compose -f compose.yaml logs -f nebula-sync
Attaching to nebula-sync
nebula-sync exited with code 139
Then is started to figure out if there is a miss match with the platform. (That's why i added this explicitly to the compose file).
> sudo docker pull --platform linux/amd64 ghcr.io/lovelaze/nebula-sync:latest
latest: Pulling from lovelaze/nebula-sync Digest: sha256:e6bb9ac7dbf4471b066cb5db74929c6fa7cfa2251a0682fa85f6da8f687ba4bf
Status: Image is up to date for ghcr.io/lovelaze/nebula-sync:latest ghcr.io/lovelaze/nebula-sync:latest
> sudo docker image inspect ghcr.io/lovelaze/nebula-sync:latest --format 'arch={{.Architecture}} os={{.Os}} id={{.Id}}'
arch=amd64 os=linux id=sha256:9e26455ba3bd5cc19bede83e41227c62bf27955ce8fb09267d8b72710adbdaef
Since my uname -m is x86_64. That should be fine.
When I try
> sudo docker run --rm -it --platform linux/amd64 -e TZ=Europe/Berlin ghcr.io/lovelaze/nebula-sync:latest nebula-sync run
it brings up no error.
So... i think that nebular is having no issues running into the main path and do the error handling for not seeing the correct set of envs and "just" return. Maybe, there is something when it seriously starting up that is causing a segfault.
Expected Behaviour
It should not fire segfault (139)
Nebula-sync Version
v0.11.1
Runtime
docker
Operating System
Synology DSM
CPU Architecture
x86_64
Configuration
services: nebula-sync:
image: ghcr.io/lovelaze/nebula-sync:latest
container_name: nebula-sync
platform: linux/amd64
environment:
- PRIMARY=http://192.168.0.88|pwd
- REPLICAS=http://192.168.0.89|pwd
- FULL_SYNC=true
- RUN_GRAVITY=true
- CRON=0 * * * * networks: {}Relevant log output
Attaching to nebula-sync
nebula-sync exited with code 139
Pi-hole Version
2025.11.1
What happened?
I started with nebular-sync and used the compose from the README.
When starting that compose it results in error 139.
Then is started to figure out if there is a miss match with the platform. (That's why i added this explicitly to the compose file).
Since my
uname -misx86_64. That should be fine.When I try
it brings up no error.
So... i think that nebular is having no issues running into the main path and do the error handling for not seeing the correct set of envs and "just" return. Maybe, there is something when it seriously starting up that is causing a segfault.
Expected Behaviour
It should not fire segfault (139)
Nebula-sync Version
v0.11.1
Runtime
docker
Operating System
Synology DSM
CPU Architecture
x86_64
Configuration
services: nebula-sync: image: ghcr.io/lovelaze/nebula-sync:latest container_name: nebula-sync platform: linux/amd64 environment: - PRIMARY=http://192.168.0.88|pwd - REPLICAS=http://192.168.0.89|pwd - FULL_SYNC=true - RUN_GRAVITY=true - CRON=0 * * * * networks: {}Relevant log output
Pi-hole Version
2025.11.1