Request: Official ctrld build for MikroTik RouterOS container (ARM64)

[andmar197264]

Hi ControlD team,

I would like to request an official ctrld build that works reliably inside a MikroTik RouterOS container environment (ARM64).

Environment

• Device: MikroTik RB5009 / CCR series
• OS: RouterOS v7.x
• Architecture: ARM64
• Deployment method: RouterOS container
• Networking: veth interface, standard NAT, no special capabilities

Current situation

• ctrld v1.4.8 (community-recompiled ARM64 binary) works perfectly on MikroTik when run as a container.
• Newer official ARM64 releases (including v1.4.9) do not work correctly in the same environment.
• The container starts, but endpoint status becomes unstable / yellow, and DNS behavior is inconsistent.

Working example (v1.4.8)

This is the exact container command that works reliably:

/container add
name=ctrld
file=ctrld_v1.4.8.tar
interface=veth-ctrld
root-dir=ctrld
workdir=/
cmd=”–cd=”
start-on-boot=yes

This binary was recompiled by a community member specifically for MikroTik RouterOS and runs without issues.

Request

Could you please:

• Provide an official ctrld build that is compatible with MikroTik RouterOS containers (ARM64), or
• Document the required build flags / dependencies needed for RouterOS compatibility.

MikroTik routers are widely used in advanced home and SMB networks, and ctrld is an excellent fit for DNS-based routing and filtering in these environments.

Thank you for your work and support.

[cuonglm]

The container starts, but endpoint status becomes unstable / yellow, and DNS behavior is inconsistent.

Could you please provide more details, e.g. ctrld logs when the issue happened.

[andmar197264]

Hi ControlD team,

Thank you for looking into this issue.

I want to clarify the situation to avoid confusion: the setup is currently WORKING STABLY on MikroTik RouterOS (ARM64) using a community-recompiled ctrld v1.4.8 binary.

Important context and observations:

Environment

• Device: MikroTik RB5009 / CCR series
• OS: RouterOS v7.x
• Architecture: ARM64
• Deployment: RouterOS container (not a standard Linux distro)
• Networking: veth interface, standard NAT, no elevated capabilities

Current status

• ctrld v1.4.8 (community-recompiled specifically for MikroTik RouterOS) works reliably and continuously.
• Newer official ARM64 releases (v1.4.9 and later) start, but the endpoint becomes unstable (yellow) and DNS behavior is inconsistent.
• The container itself does NOT crash in either case.

Critical detail (very important)

• For MikroTik RouterOS, the ControlD “Legacy Resolver” option MUST be enabled.
• With Legacy Resolver enabled, ctrld v1.4.8 stays stable and the endpoint remains Active.
• Without Legacy Resolver, newer official builds tend to become unstable even though the container is running.

Working example (v1.4.8)
This is the exact container configuration that works reliably:

/container add
name=ctrld
file=ctrld_v1.4.8.tar
interface=veth-ctrld
root-dir=ctrld
workdir=/
cmd="--cd=XXXX"
start-on-boot=yes

RouterOS logs from the working setup show normal behavior only:

• ctrld starts
• internal logging enabled
• no crashes, no abnormal exits

Why we did not provide failure logs
This router is a production system. We intentionally do NOT want to replace a stable working setup just to reproduce failures with newer builds.

The problem does not appear to be a runtime crash, but rather a compatibility issue between:

• RouterOS container limitations
• networking / resolver behavior
• changes introduced in official builds after v1.4.8

Request
We kindly ask if you could:

• Compare build flags / dependencies between official v1.4.9+ and the working v1.4.8 build, or
• Provide guidance on required build flags or runtime expectations for RouterOS container compatibility, or
• Offer an experimental/custom build of v1.4.9+ suitable for MikroTik RouterOS (ARM64), which we will gladly test.

MikroTik routers are widely used in advanced home and SMB networks, and ctrld is an excellent fit for DNS-based routing and filtering on these platforms.

Thank you for your work and support.