Builder for a UEFI-enabled RouterOS CHR image using GitHub Action.
[!TIP] If these images are required on some virtualized platform/cloud, and Mikrotik's official downloads DO NOT WORK on same platform - please let me know either as issue here or on Mikrotik's forum – as I've been collecting data. The current summary is:
- Apple Virtualization Framework On Intel, all images should work. On ARM-based M1/M2/M3, none have been reported to work.
- Vultr - Mikrotik images only work because the instructions suggest SystemRescueCD and
dd, reported that the "@jaclaz method" (used in all post-7.15 releases work without Mikrotik's "ddapproach", see this post- Oracle Cloud using ARM64/Amprere Reported that experimental ARM64 7.17beta2 image worked (all other packages are Intel-only). See @BetaQuasi comment in https://github.com/tikoci/fat-chr/issues/5#issuecomment-2394976574
Mikrotik's virtual machine version of RouterOS ("CHR") is downloadable as a RAW image. However, this image is incompatible with UEFI-based bootloaders. Specifically, Apple's Virtualization Framework for Intel-based MacOS to run RouterOS CHR
Non-EUFI raw images for "stable" and "testing" for latest version are downloaded. CI will convert the partitioning scheme from EXT2 to FAT16 using gdisk & publish as a release.
There is "workflow_dispatch" on the "Build and Release" to manual trigger a specific build to fetch older/specific versions & select a script to run. All builds marked as "pre-release" in Releases and must be manually changed to remove the flag. No check is done if a version was already build, so duplicates can be deleted manually.
gdisk. This script is used in CHR 7.15 and above images.ext2 to fat of the EFI partition. One use case for the CHR images here is Apple Virtualization support, which just need EFI partition to be fat (i.e. MacOS has no support for mounting ext2, and per UEFI specs it should be fat).