Skip to content

Docker Container On Unraid Server Not working from 1.4.7+ #272

@mrbell-dev

Description

@mrbell-dev

ControlD Bug Report: Version 1.4.8 Issue

Environment

  • Docker container on Unraid
  • Network: Bridge mode (br0) with static IP
  • Time Zone: America/New_York

Docker Run Command (Sanitized)

docker run -d \
  --name='ctrld-failover' \
  --net='br0' \
  --ip='192.168.69.169' \
  --pids-limit 2048 \
  -e TZ="America/New_York" \
  -e HOST_OS="Unraid" \
  -e HOST_HOSTNAME="UnRaid-Server" \
  -e HOST_CONTAINERNAME="ctrld-failover" \
  -l net.unraid.docker.managed=dockerman \
  -l net.unraid.docker.icon='https://avatars.githubusercontent.com/u/108295153' \
  'controldns/ctrld:debug' \
  --cd=REDACTED_CONFIG_ID \
  -vv

Issue Description

Version 1.4.6 works correctly, but version 1.4.8 exhibits problems.


WORKING VERSION - 1.4.6 Logs (Selected Excerpts)

Dec  8 13:51:53.841 DBG found hostname: "Device-1", ip: "fe80::1838:ab4f:3ce5:dcb6" via mdns
Dec  8 13:51:53.841 DBG found hostname: "Device-1", ip: "192.168.68.56" via mdns
Dec  8 13:51:53.841 DBG found hostname: "Device-1", ip: "fdaa:5240:b20a:5645:1075:1d40:4e28:d084" via mdns
Dec  8 13:51:53.952 DBG found hostname: "Device-2", ip: "192.168.68.59" via mdns
Dec  8 13:51:53.952 DBG found hostname: "Device-2", ip: "fe80::c2b5:d7ff:fe2a:4a3a" via mdns
Dec  8 13:51:54.024 DBG found hostname: "Device-3", ip: "192.168.68.88" via mdns
Dec  8 13:51:54.103 DBG os resolver query for 85.68.168.192.in-addr.arpa. with nameservers: [] public: []
Dec  8 13:51:54.103 INF could not perform PTR lookup error="no nameservers available for query" discovery=ptr
Dec  8 13:51:54.103 INF [5002bd] QUERY: 192.168.68.85:62654 (192.168.68.85) -> listener.0: AAAA f360sc.prd.fusionapi.autodesk.com
Dec  8 13:51:54.103 INF [3b67c2] QUERY: 192.168.68.85:55979 (192.168.68.85) -> listener.0: A f360sc.prd.fusionapi.autodesk.com
Dec  8 13:51:54.103 DBG [3b67c2] no explicit policy matched, using default routing -> [upstream.0]
Dec  8 13:51:54.104 DBG os resolver query for . with nameservers: [] public: []
Dec  8 13:51:54.104 DBG [3b67c2] including client info with the request
Dec  8 13:51:54.104 DBG [3b67c2] sending query to upstream.0: 
Dec  8 13:51:54.103 DBG [5002bd] no explicit policy matched, using default routing -> [upstream.0]
Dec  8 13:51:54.104 DBG [3b67c2] sending request header: map[X-Cd-Host:[192.168.68.85] X-Cd-Ip:[192.168.68.85]]
Dec  8 13:51:54.104 DBG [5002bd] including client info with the request
Dec  8 13:51:54.104 DBG [5002bd] sending query to upstream.0: 
Dec  8 13:51:54.104 DBG [5002bd] sending request header: map[X-Cd-Host:[192.168.68.85] X-Cd-Ip:[192.168.68.85]]
Dec  8 13:51:54.116 DBG os resolver query for . with nameservers: [] public: []
Dec  8 13:51:54.118 INF [68ad0c] QUERY: 192.168.68.85:65221 (192.168.68.85) -> listener.0: A edge.microsoft.com
Dec  8 13:51:54.118 DBG [68ad0c] no explicit policy matched, using default routing -> [upstream.0]
Dec  8 13:51:54.118 INF [358d38] QUERY: 192.168.68.85:50591 (192.168.68.85) -> listener.0: AAAA edge.microsoft.com
Dec  8 13:51:54.118 DBG [358d38] no explicit policy matched, using default routing -> [upstream.0]
Dec  8 13:51:54.118 DBG [68ad0c] including client info with the request
Dec  8 13:51:54.118 DBG [68ad0c] sending query to upstream.0: 
Dec  8 13:51:54.118 DBG [358d38] including client info with the request
Dec  8 13:51:54.118 DBG [358d38] sending query to upstream.0: 
Dec  8 13:51:54.118 DBG [68ad0c] sending request header: map[X-Cd-Host:[192.168.68.85] X-Cd-Ip:[192.168.68.85]]
Dec  8 13:51:54.119 DBG [358d38] sending request header: map[X-Cd-Host:[192.168.68.85] X-Cd-Ip:[192.168.68.85]]
Dec  8 13:51:54.174 DBG os resolver query for . with nameservers: [] public: []
Dec  8 13:51:54.177 INF [358d38] REPLY: upstream.0 -> 192.168.68.85:50591 (192.168.68.85): NOERROR
Dec  8 13:51:54.177 INF [68ad0c] REPLY: upstream.0 -> 192.168.68.85:65221 (192.168.68.85): NOERROR
Dec  8 13:51:54.177 DBG [358d38] received response of 160 bytes in 59.144721ms
Dec  8 13:51:54.177 DBG [68ad0c] received response of 136 bytes in 59.163141ms
Dec  8 13:51:54.208 INF [5002bd] REPLY: upstream.0 -> 192.168.68.85:62654 (192.168.68.85): NOERROR
Dec  8 13:51:54.208 DBG [5002bd] received response of 172 bytes in 104.785337ms
Dec  8 13:51:54.211 INF [3b67c2] REPLY: upstream.0 -> 192.168.68.85:55979 (192.168.68.85): NOERROR
Dec  8 13:51:54.211 DBG [3b67c2] received response of 158 bytes in 107.405131ms
Dec  8 13:51:54.240 DBG os resolver query for . with nameservers: [] public: []
Dec  8 13:51:54.329 DBG found hostname: "Device-4", ip: "192.168.68.93" via mdns
Dec  8 13:51:54.423 DBG os resolver query for . with nameservers: [] public: []
Dec  8 13:51:54.664 DBG os resolver query for . with nameservers: [] public: []
Dec  8 13:51:54.787 INF [3ac238] QUERY: 192.168.68.85:56222 (192.168.68.85) -> listener.0: A js.prd.fusionapi.autodesk.com
Dec  8 13:51:54.787 DBG [3ac238] no explicit policy matched, using default routing -> [upstream.0]
Dec  8 13:51:54.787 DBG [3ac238] including client info with the request
Dec  8 13:51:54.787 DBG [3ac238] sending query to upstream.0: 
Dec  8 13:51:54.787 DBG [3ac238] sending request header: map[X-Cd-Host:[192.168.68.85] X-Cd-Ip:[192.168.68.85]]
Dec  8 13:51:54.787 INF [30dd68] QUERY: 192.168.68.85:63837 (192.168.68.85) -> listener.0: AAAA js.prd.fusionapi.autodesk.com
Dec  8 13:51:54.787 DBG [30dd68] no explicit policy matched, using default routing -> [upstream.0]
Dec  8 13:51:54.787 DBG [30dd68] including client info with the request
Dec  8 13:51:54.787 DBG [30dd68] sending query to upstream.0: 
Dec  8 13:51:54.787 DBG [30dd68] sending request header: map[X-Cd-Host:[192.168.68.85] X-Cd-Ip:[192.168.68.85]]
Dec  8 13:51:54.814 INF [3ac238] REPLY: upstream.0 -> 192.168.68.85:56222 (192.168.68.85): NOERROR
Dec  8 13:51:54.814 DBG [3ac238] received response of 154 bytes in 27.320365ms
Dec  8 13:51:54.818 INF [30dd68] REPLY: upstream.0 -> 192.168.68.85:63837 (192.168.68.85): NOERROR

FAILING VERSION - 1.4.8 Debug Logs

Dec  8 13:50:58.000 INF writing default config file to: /ctrld.toml
Dec  8 13:50:58.099 NTC internal logging enabled
Dec  8 13:50:58.099 INF starting ctrld v1.4.8
Dec  8 13:50:58.099 INF os: linux 6.12.54-Unraid
Dec  8 13:50:58.099 INF fetching Controld D configuration from API: REDACTED_CONFIG_ID mode=cd
Dec  8 13:50:58.099 DBG Initialize new OS resolver with default nameservers
Dec  8 13:50:58.100 DBG resolving "api.controld.com" using bootstrap DNS ["127.0.0.11:53"]
Dec  8 13:50:58.100 DBG os resolver query for api.controld.com. with nameservers: [127.0.0.11:53] public: []
Dec  8 13:50:58.119 DBG using LAN answer from: 127.0.0.11:53
Dec  8 13:50:58.119 DBG got answer from nameserver: 127.0.0.11
Dec  8 13:50:58.119 DBG os resolver query for api.controld.com. with nameservers: [127.0.0.11:53] public: []
Dec  8 13:50:58.133 DBG using LAN answer from: 127.0.0.11:53
Dec  8 13:50:58.133 DBG got answer from nameserver: 127.0.0.11
Dec  8 13:50:58.133 DBG dialing to 147.185.34.1:443
Dec  8 13:50:58.151 DBG connected to 147.185.34.1:443
Dec  8 13:50:58.347 INF generating ctrld config from Control-D configuration mode=cd
Dec  8 13:50:58.347 INF using defined custom config of Control-D resolver mode=cd
Dec  8 13:50:58.347 INF writing config file to: ctrld.toml
Dec  8 13:50:58.348 DBG control server started: /var/run/ctrld_control.sock
Dec  8 13:50:58.348 DBG resolving "dns.controld.com" using bootstrap DNS ["127.0.0.11:53"]
Dec  8 13:50:58.348 DBG os resolver query for dns.controld.com. with nameservers: [127.0.0.11:53] public: []
Dec  8 13:50:58.376 DBG using LAN answer from: 127.0.0.11:53
Dec  8 13:50:58.376 DBG got answer from nameserver: 127.0.0.11
Dec  8 13:50:58.376 DBG os resolver query for dns.controld.com. with nameservers: [127.0.0.11:53] public: []
Dec  8 13:50:58.392 DBG using LAN answer from: 127.0.0.11:53
Dec  8 13:50:58.392 DBG got answer from nameserver: 127.0.0.11
Dec  8 13:50:58.392 DBG bootstrap IPs: [2606:1a40::22 76.76.2.22]
Dec  8 13:50:58.392 INF bootstrap IPs for upstream.0: ["2606:1a40::22" "76.76.2.22"]
Dec  8 13:50:58.392 DBG checking for IPv6 availability once
Dec  8 13:50:58.392 DBG ipv6 availability: false
Dec  8 13:50:58.392 DBG checking default route interface iface=eth0
Dec  8 13:50:58.392 DBG found ip with default route interface ip=192.168.69.169
Dec  8 13:50:58.392 DBG start hosts file discovery
Dec  8 13:50:58.392 INF starting DNS server on listener.0: 127.0.0.1:53
Dec  8 13:50:58.392 DBG start dhcp discovery
Dec  8 13:50:58.393 DBG start checking DNS loop
Dec  8 13:50:58.393 DBG skipping external: upstream.0
Dec  8 13:50:58.393 DBG dialing to 76.76.2.22:443
Dec  8 13:50:58.393 DBG end checking DNS loop
Dec  8 13:50:58.393 DBG starting custom config reload timer mode=api-reload
Dec  8 13:50:58.393 DBG Network monitor started
Dec  8 13:50:58.393 DBG start arp discovery
Dec  8 13:50:58.394 DBG start ptr discovery
Dec  8 13:50:58.394 DBG start mdns discovery
Dec  8 13:50:58.394 DBG checking for IPv6 availability in mdns init
Dec  8 13:50:58.394 DBG IPv6 is false in mdns init
Dec  8 13:50:58.394 DBG could not find avahi-browse binary, skipping. error="exec: \"avahi-browse\": executable file not found in $PATH"
Dec  8 13:50:58.406 DBG connected to 76.76.2.22:443
Dec  8 13:50:58.406 DBG sending doh request to: 76.76.2.22:443
Dec  8 13:50:58.492 DBG found hostname: "Device-1", ip: "fe80::1838:ab4f:3ce5:dcb6" via mdns
Dec  8 13:50:58.492 DBG found hostname: "Device-1", ip: "192.168.68.56" via mdns
Dec  8 13:50:58.492 DBG found hostname: "Device-1", ip: "fdaa:5240:b20a:5645:1075:1d40:4e28:d084" via mdns
Dec  8 13:50:58.503 DBG found hostname: "Device-MAC-1", ip: "192.168.68.97" via mdns
Dec  8 13:50:58.505 DBG update hostname: "Device-UUID-1", ip: "192.168.68.97", old: "Device-MAC-1" via mdns
Dec  8 13:50:58.546 DBG found hostname: "Device-5", ip: "fe80::c25:5876:c793:820f" via mdns
Dec  8 13:50:58.546 DBG found hostname: "Device-5", ip: "192.168.68.54" via mdns
Dec  8 13:50:58.546 DBG found hostname: "Device-5", ip: "fdaa:5240:b20a:5645:4:fdd4:28fe:ef42" via mdns
Dec  8 13:50:58.546 DBG found hostname: "Device-5", ip: "fdaa:5240:b20a:5645:140c:6dbc:b238:af70" via mdns
Dec  8 13:50:58.606 DBG update hostname: "Device-6", ip: "192.168.68.97", old: "Device-UUID-1" via mdns
Dec  8 13:50:58.606 DBG found hostname: "Device-6", ip: "fdaa:5240:b20a:5645:cc9c:60d7:9e3d:ff3b" via mdns
Dec  8 13:50:58.606 DBG found hostname: "Device-6", ip: "fe80::ba1b:4efa:790:82b9" via mdns
Dec  8 13:50:58.606 DBG found hostname: "Device-6", ip: "fdaa:5240:b20a:5645:3230:ed32:ae90:50bf" via mdns
Dec  8 13:50:58.613 DBG found hostname: "Device-7", ip: "fe80::4b1:fa7:29ca:6649" via mdns
Dec  8 13:50:58.613 DBG found hostname: "Device-7", ip: "192.168.68.80" via mdns
Dec  8 13:50:58.613 DBG found hostname: "Device-7", ip: "fdaa:5240:b20a:5645:497:39ee:6f0b:591d" via mdns
Dec  8 13:50:58.763 DBG found hostname: "Device-3", ip: "192.168.68.88" via mdns
Dec  8 13:50:59.151 DBG found hostname: "Device-4", ip: "192.168.68.93" via mdns
Dec  8 13:50:59.155 DBG found hostname: "Device-8", ip: "192.168.68.98" via mdns
Dec  8 13:50:59.155 DBG found hostname: "Device-8", ip: "fdaa:5240:b20a:5645:4661:32ff:fe57:2c" via mdns
Dec  8 13:50:59.155 DBG found hostname: "Device-8", ip: "fe80::4661:32ff:fe57:2c" via mdns
Dec  8 13:50:59.468 DBG found hostname: "Device-2", ip: "192.168.68.59" via mdns
Dec  8 13:50:59.468 DBG found hostname: "Device-2", ip: "fe80::c2b5:d7ff:fe2a:4a3a" via mdns
Dec  8 13:51:05.611 DBG found hostname: "Device-9", ip: "192.168.68.85" via mdns
Dec  8 13:51:05.611 DBG found hostname: "Device-9", ip: "fdaa:5240:b20a:5645:d005:b9c8:93bc:5e4b" via mdns
Dec  8 13:51:05.611 DBG found hostname: "Device-9", ip: "fdaa:5240:b20a:5645:6123:b887:a5d0:d7d1" via mdns
Dec  8 13:51:05.611 DBG found hostname: "Device-9", ip: "fe80::80f5:7a66:f6e5:db1c" via mdns
Dec  8 13:51:53.696 DBG update hostname: "Device-MAC-1", ip: "192.168.68.97", old: "Device-6" via mdns
Dec  8 13:51:53.697 DBG update hostname: "Device-UUID-1", ip: "192.168.68.97", old: "Device-MAC-1" via mdns
Dec  8 13:51:53.766 DBG update hostname: "Device-6", ip: "192.168.68.97", old: "Device-UUID-1" via mdns
Dec  8 13:51:58.393 DBG start checking DNS loop
Dec  8 13:51:58.393 DBG skipping external: upstream.0
Dec  8 13:51:58.393 DBG end checking DNS loop
Dec  8 13:52:58.393 DBG start checking DNS loop
Dec  8 13:52:58.393 DBG skipping external: upstream.0
Dec  8 13:52:58.393 DBG end checking DNS loop
Dec  8 13:53:30.078 DBG update hostname: "Device-UUID-1", ip: "192.168.68.97", old: "Device-6" via mdns
Dec  8 13:53:58.394 DBG start checking DNS loop
Dec  8 13:53:58.394 DBG skipping external: upstream.0
Dec  8 13:53:58.394 DBG end checking DNS loop

Key Observations

  1. Version 1.4.6: Shows DNS queries being processed successfully with replies
  2. Version 1.4.8: Shows mDNS discovery working but lacks the actual DNS query/reply traffic seen in 1.4.6
  3. Both versions discover devices via mDNS successfully
  4. Version 1.4.8 appears to start normally but may not be processing DNS queries properly

Additional Notes

  • IPv6 availability: false (both versions)
  • Network interface: eth0
  • Container IP: 192.168.69.169
  • DNS server listening on: 127.0.0.1:53
  • Bootstrap DNS: Personal ControlD IP

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions