*   [2024 hEX Refresh](https://mikrotik.com/product/hex_2024)
*   [2025 hEX S Refresh](https://mikrotik.com/product/hex_s_2025)

These will run `container.npk`, but because there are [nearly zero][^v5img] available container images available, your options will be strongly constrained unless you're willing to do the work of porting containers yourself. Fortunately, unlike with the legacy CPU types mentioned above, [there do exist a good number of base container images][arm32v5] to get started with. The most broadly useful is [their `debian` image][v5deb].

The broader points remain true: if you start with a container that does something _other_ than `FROM debian:…` in its `Dockerfile`, changing that line to refer instead to `arm32v5:debian` and rebuilding is unlikely to work. You're in for a manual porting effort.

For perspective, the Raspberry Pi foundation selected a chip using the ARMv6 architecture for their initial product offering in 2012, then switched to the ARMv7 architecture for the Pi 2 and newer. ARMv5 is _seriously old tech!_
For perspective, the Raspberry Pi foundation selected a chip using the ARMv6 architecture for their initial product offering in 2012, then switched to the ARMv7 architecture for the Pi 2 and newer, then ARMv8 (a.k.a. aarch64 or ARM64) for the Pi 4 and newer. ARMv5 is _seriously old tech!_

[^v5img]: As of this writing, an [architecture search for “armv5” on Docker Hub](https://hub.docker.com/search?architecture=armv5) returns zero results, but in the past, it returned a small number, approximately five, as I recall. None were for mainstream Linux distros, the type most useful as an image base.

[arm32v5]: https://hub.docker.com/u/arm32v5
[v5deb]:   https://hub.docker.com/r/arm32v5/debian