debug token is: https://tricorder.pi-hole.net/GlIMDMHD/
*** [ DIAGNOSING ]: Pi-hole processes
[✗] lighttpd daemon is inactive
[✗] pihole-FTL daemon is inactive
*** [ DIAGNOSING ]: Pi-hole-FTL full status
[i] systemctl: command not found
If I attach to the container and #apt-get install systemd
(to install systemctl)
Then the lighttpd daemon issue goes away
I have to do a reboot to get systemctl working.
Is there away to tell pihole that the base os does not have systemctl? Or is it just missing from the image?
I am starting to think that despite the debug log, lighttpd and pihole-FTL are running, without the need for installing systemctl.
Within the docker containers, Pi-hole does not use systemd but s6 as init system. That's why the debug log fails to recognize the state of the services.
Docker restrictions cause the service reporting from inside a container to be less reliable than we'd wish for at times. 
Your debug log shows your Pi-hole to be fully operational, processing and blocking queries:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] jlaebacinqqpwwv.su is 0.0.0.0 on lo (127.0.0.1)
[✓] jlaebacinqqpwwv.su is 0.0.0.0 on eth0 (192.168.1.200)
[✓] doubleclick.com is 142.251.215.238 via a remote, public DNS server (8.8.8.8)
You may safely ignore those sections from the debug log.