https://docs.controld.com/discuss/66370aa3ffc672000fcb224f
please let me know if anyone was successful
here is a way to get past controld arm docker image issue,
build image yourself.
on a linux box:
cd github
git clone https://github.com/Control-D-Inc/ctrld.git
cd ctrld;
env GOOS=linux GOARCH=arm go build -a -gcflags=“all=-l -B” -ldflags=“-w -s” ./cmd/ctrld
cd ..
docker run --privileged --rm tonistiigi/binfmt --install all
docker buildx ls #make sure your target architecture shows up
mkdir dockerbuildcustom
cd dockerbuildcustom
cp github/ctrld/ctrld generated to current folder
create simple DockerFile that uses alpine and copies the ctrld binary with entry point as ctrld.
docker ls
docker images
docker buildx build --no-cache --platform arm --output=type=docker -t ctrld136:arch .
docker save ctrld136 > ../ctrld136_arm.tar
move above file to mikrotik and use it for container creation.
also use mounts as part of container creation with /etc/controld destination pointing to local location in router where there is config.toml
am having issues though reaching the container that has controld running(veth port to a controldbridge) from my main vlan aware(bridge vlan filtering enabled) bridge where my devices are. ping from devices on my main bridge cannot reach the ip of veth (while i can ping it using tools->ping). any help at high level would be appreciated
Put the VETH in LAN interface list, otherwise default firewall will drop the traffic.