MikroTik Solutions

Changes To Container Limitations
Login

Changes To Container Limitations

Changes to "Container Limitations" between 2025-07-20 21:27:19 and 2025-07-26 01:48:22

309
310
311
312
313
314
315
316

317
318

319
320
321
322
323
324
325
309
310
311
312
313
314
315

316
317

318
319
320
321
322
323
324
325







-
+

-
+







There’s a special case to be aware of here: MikroTik have released a few products now based on the EN7562 SoC, which includes a low-spec ARMv5 core:

*   [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.
The general points above 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, then ARMv8 (a.k.a. aarch64 or ARM64) for the Pi 4 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 3, then ARMv8 (a.k.a. aarch64 or ARM64) for the Pi 4 and 5. 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