I can offer a self-service solution to building them…
FWIW, you/anyone to rebuild the image using any script with GitHub running it using “GitHub Actions”.
Basically, the steps to “Creating your own CHR builder” are:
-
Use/create a GitHub account (free & as long as your repo/project is public, you get decent number of “free minutes” to run builds)
-
Use the “Fork” option from GitHub - tikoci/fat-chr: Builder for CHR images with UEFI support (testing) to create your own copy:
-
In your new repo/fork, within your “Setting” for the repo, you’ll need to enable GitHub Actions (by default, there disabled for Forks):
-
GitHub has nifty feature to bring “VSCode for Web” by just hitting the . (dot) key while viewing your repo in a web browser. This allows you to edit a script or build actions (in .github/workflows/manual.yaml). You can create a new script file in the root with any new/desired steps, or just modify any of the exist script (no-gdisk, jclaz, etc). If you change one, go to the Git icon on left to “commit” and changes to the script.
So you don’t have to leave the web to build these things…and have a repeatable process as a result -
In you main fork’s main GitHub page (not VSCode view), you can go to “Actions”, click the “Manual Build and Release”, then use the “Run workflow” button to pick the RouterOS version and “mod script” file name to run as part of the build. For X86 leave “arch” blank (and use “arm64” when building arm, but only the no-gdsk-arm64 script works with that option):
-
If you run the workflow from popup, a new job will appear. If you click it, then click “build” button in center, you’ll see what’s going on at each step:
-
The Release section from main project will have the images if build was successful.
