Me neither. In 15 minute test, it totally works. I started on Mac, then added /app as the 2nd peer per their cloud site. They do have interesting mix of features, like handling DNS and remote access things like builtin SSH/etc.
Internally, looks like they pull same trick (STUN/ICE + TURN/"Relay") as BackToHome with WG. It's actually similar to what I thought a "BackToWork" feature should look like as professional version of BTH.
But here is an /app for it... you just need a setup key for a peer from the Netbird website:
/app/add yaml="
name: netbird-client
services:
netbird-client:
environment:
NB_SETUP_KEY: MUST_SET_FROM_NETBIRD
NB_DISABLE_CUSTOM_ROUTING: 'true'
NB_USE_LEGACY_ROUTING: 'true'
volumes:
- netbird-client:/var/lib/netbird
image: docker.io/netbirdio/netbird:latest
"
You'll need the "setup id" from Netbird to connect. You can add it the YAML, or set it as an ENV variable in the /app.
With network id set, to enable the /app use:
/app/enable netbird-client
or click "Enable" in WinBox/WebFig. This will do the rest of container add, VETH, internal bridge, etc and auto-start it.
You can add Netbird options in the command: under the service in YAML. Or, once added, edit the "Container Command Lines" and fill in the 4th column next to netbird-client.
Now do more useful things, you'd need to think more about the network configuration.
Note: Netbird example uses some Docker cap_add stuff, that I ignored, since the RouterOS's container cgroups allow most of NET_ADMIN (AFAIK). And seems to connects. OP seems to have it working a /container so it must not be critical to set those (since you cannot on RouterOS).
Only issue was the builtin SSH did not work (even after adding policy and --allow-server-ssh --enable-ssh-root to /app command, but didn't troubleshoot it much. Now the cgroup might be involved here, but IDK. It could also be port forwarding since I'm using 22 already, but the remote SSH should use Netbird WG. As I said didn't research/test the remote SSH option much. More noting Netbird example uses SYS_ADMIN and SYS_RESOURCE previllege for Docker, in addition to more common NET_ADMIN... And MikroTik does not explain exactly how cgroups are mapped back to Docker capacities.
edit: added envs from: https://docs.netbird.io/use-cases/client-on-mikrotik-router