Wed Mar 06, 2024 9:32 pm
The Yacht looks interesting. It does all things that RouterOS doesn't with /container without all larger scale pod stuff...
I'd imagine it be possible to "port" yacht for docking on RouterOS. It is open source. Most of the interaction with docker daemon only happens in a few places in the python. So THEORITICALLY, the Docker's API (that happen via docker.sock) COULD be replace using IP to Mikrotik's API, with some work... 80% of the code looks to be UI at managing the configs and their "templating", only 20% is talking to docker.
While what images are loaded etc is possible in Mikrotik API. Getting the CPU and memory for a particular container is trickier. RouterOS does NOT have a corresponding API for that part. I suppose some theoretically "Mikrotik Yacht" could read "/proc/stat" via mount or shell from yacht backend, but that may not be full-proof since I'm not sure all image mount a /proc.
Anyway it ain't just needing a docker.sock to fix the yacht.