pihole - dev - will not stay running

[heffneil]

Versions

Core
Version is 4902c70 (Latest: null)
Branch is development
Hash is 4902c700 (Latest: efaa0f42)
Web
Version is 603f35d (Latest: null)
Branch is development
Hash is 603f35d5 (Latest: 603f35d5)
FTL
Version is vDev-f2c82da (Latest: null)
Branch is development
Hash is f2c82da9 (Latest: d01a2652)

Platform

• OS and version:
• Distributor ID: Ubuntu
  Description: Ubuntu 22.04.5 LTS
  Release: 22.04
  Codename: jammy

• Platform: Docker

Expected behavior

I believe nebula sync might be killing the container for some reason.

Actual behavior / bug

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0807661422a4 pihole/pihole:development "start.sh" 26 hours ago Up 21 hours (unhealthy)

my docker container logs can be seen here:
https://pastebin.com/tBXWsv2u

Debug Token

• URL: https://tricorder.pi-hole.net/BP1NU4C7/

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

[rdwebdesign]

I believe nebula sync might be killing the container for some reason.

If an external program is killing the container, then this is 100% out of Pi-hole control.

---

Probably unrelated to your issue, but if you want to use or test Pi-hole v6 (Core + FTL + Web), you should use nightly tag.

The image tagged as development should only be used when you are developing/testing docker-pi-hole code.

[heffneil]

I don't know for sure thats why I posed the results. I am currently not querying the name server just trying to establish the infrastructure and make it reliable. The only thing working on this server is the sync from the other server which leads me to believe it is the sync but I was hoping the logs I provided might give some insight and clarity.

[rdwebdesign]

Your pastebin shows Pi-hole was terminated at 00:55:

2025-01-15 00:55:00.407 EST [50M] INFO: Asked to terminate by "/usr/bin/pihole-FTL no-daemon" (PID 50, user pihole UID 100)

Your debug log shows Pi-hole was running without issues at 2025-01-15 19:10.

[heffneil]

I had to restart it in order to do the logs so that is why the debug was running at that time. The docker container shows unhealthy prior to the restart and there are no other logs between 00:55 and when I restarted?

[heffneil]

I left nebula-sync off overnight and the container continues to run. I think this might be something to do with nebula-sync but all I can imagine it does is copy files from one server to another so something in that process is causing a hiccup.

[lovelaze]

I believe nebula sync might be killing the container for some reason.

If an external program is killing the container, then this is 100% out of Pi-hole control.

The external application here is pretty much just sending a GET /teleporter to one pihole and then a POST /teleporter with the first respose as payload to another pihole.