Add support for Mikrotik CHR arm64 images

[mpfz0r]

• Adjust vrnetlab to support aarch64.
• Bump routeros docker image to debian trixie for newer more performant qemu version
• Install python 3.12 with uv. To keep backwards compatibility
• add cross platform build support to makefile.include (via DOCKER_PLATFORM variable)

[mischadiehm]

works great and so much faster on my macbp!

md@debian-clab:/Users/md/git/narrowin-labs/ot-lab$ docker ps | grep mikrotik
86009b90de33   vrnetlab/mikrotik_routeros:7.20.6-arm64    "uv run /[launch.py](http://launch.py/) -…"   2 minutes ago        Up 2 minutes (healthy)          22/tcp, 830/tcp, 5000/tcp, 5678/tcp, 8291/tcp, 10000-10099/tcp, 161/udp   clab-ot-sec-flat-sw-acc2
9877277669f4   vrnetlab/mikrotik_routeros:7.20.6-arm64    "uv run /[launch.py](http://launch.py/) -…"   2 minutes ago        Up 2 minutes (healthy)          22/tcp, 830/tcp, 5000/tcp, 5678/tcp, 8291/tcp, 10000-10099/tcp, 161/udp   clab-ot-sec-flat-gw-firewall
81b584e51030   vrnetlab/mikrotik_routeros:7.20.6-arm64    "uv run /[launch.py](http://launch.py/) -…"   2 minutes ago        Up 2 minutes (healthy)          22/tcp, 830/tcp, 5000/tcp, 5678/tcp, 8291/tcp, 10000-10099/tcp, 161/udp   clab-ot-sec-flat-sw-acc1
831b4beed6fa   vrnetlab/mikrotik_routeros:7.20.6-arm64    "uv run /[launch.py](http://launch.py/) -…"   2 minutes ago        Up 2 minutes (healthy)          22/tcp, 830/tcp, 5000/tcp, 5678/tcp, 8291/tcp, 10000-10099/tcp, 161/udp   clab-ot-sec-flat-sw-dist

[mpfz0r]

also tested on amd64 now. I consider this done

[mischadiehm]

@mpfz0r not sure if using -arm64 is best choice when trying to make this as easy to use as possible you might wanna get rid of the dash?

export ARCH=arm64

# then in the clab config you would do sth like:
    #image: vrnetlab/mikrotik_routeros:7.20.6
    #image: vrnetlab/mikrotik_routeros:7.20.6-arm64 the dash here breaks this simple env switch
    image: vrnetlab/mikrotik_routeros:7.20.6{ARCH}
    restart-policy: "no"

which fails when you want simple env switches unless one does:

export ARCH="-arm64"

which is also kind of awkward? So if you create the image without the - we loose a bit readability but do gain quite some simple flexibility

[mpfz0r]

I would've like to keep this a semantic version. I'm either gonna tag the amd64 image with an additional tag -amd64 for consistency, or maybe I can try and make this a multi-arch image.
hang in there..

[mpfz0r]

I've added this and also cross platform build support, so you dont need to resort to two machines when building this.
This is the new format:

vrnetlab/mikrotik_routeros:7.20.4                                     43e6c174249e        479MB          479MB
vrnetlab/mikrotik_routeros:7.20.4-amd64                               43e6c174249e        479MB          479MB
vrnetlab/mikrotik_routeros:7.20.4-arm64                               e210346fe2d3       2.27GB          442MB

I've started looking into multi-arch images, but since this needs a running registry, I think this doesn't necessarily need to be implemented in vrnetlab.