True, but your customers have bought them, and some number of them still work. I believe the motivation behind this thread is that some subset of these customers want to stretch their useful lifetimes by using them as container runners.
(For what it’s worth, I don’t own any TILE-based MT products. I’m speaking here from experience building containers and other software, not out of any personal need for this feature to exist.)
kernel support has been discontinued
MikroTik ported the patches necessary forward into RouterOS 7, solving the deployment case.
A TILE-supporting CPU isn’t needed at build or emulation time, because containers use the host OS’s kernel. Syscalls are resolved by call number, not by memory address or anything else CPU-specific. mkdir(2) is syscall #83 on every Linux distro regardless of CPU type, for example. This allows in-container calls into the kernel to be mapped to calls into the host’s kernel.
Is it worth investing time in it now?
My premise is that MT’s slice of the work is merely to produce a build of container.npk, then support it in the way they do all other NPKs. Everything else is left up to the FOSS community. Would you be willing to provide that build and chase bugs?
If not, then kevinds is right, and it doesn’t matter how much work the FOSS community is willing to do to make this a reality.