Installing V2Ray or similar container on hAP ax s – Feasibility and guidance

RouterOS Containers
1

Hello MikroTik Community,

I am trying to run a V2Ray container (or any similar proxy service) on my hAP ax S device, with all files stored on a USB drive (/usb1) to avoid using internal storage.

I have attempted using the "teddysun/v2ray:latest" image, but it exited immediately with "Illegal instruction". I suspect this is due to CPU architecture compatibility (ARM32 vs ARM64).

Here is my device information:

  • RouterOS version: 7.22beta5 (testing)
  • Board name: hAP ax S
  • CPU: ARM, 2 cores
  • Total memory: 512 MB
  • Free memory: 410 MB
  • Total storage: 128 MB
  • Free storage: 76 MB

My questions:

  1. Is it feasible to run V2Ray (or Xray) on hAP ax S using containers with all files on USB?
  2. Are there specific ARM32-compatible images recommended for this device?
  3. Are there best practices for CPU/RAM-limited MikroTik models when running proxy containers?

Any advice or guidance would be highly appreciated. Thank you!

2

Those aren’t the only two choices. Read this, then note that the images you refer to stop at linux/arm/v6.

If you don’t like the advice at the first link — port it yourself — I advise that you either get a more capable device or limit your usage to what comes built-in, like Wireguard.

3

Thanks for the clarification.

You are right — ARM32 vs ARM64 is an oversimplification, and the Docker images I tested indeed only go up to linux/arm/v6, which explains the illegal instruction issue on this platform.

At this point, my main goal was to understand whether anyone has successfully run any userland proxy (V2Ray/Xray or similar) on hAP ax S specifically, or if the practical limitations of RouterOS containers on this architecture make it unrealistic without self-porting.

Porting it myself is technically possible, but given the device constraints (ARM architecture, limited storage, RouterOS container environment), I wanted to confirm first whether this is a known dead end on this model.

If the consensus is that hAP ax S is not a good candidate for such workloads, I agree that sticking to built-in features like WireGuard or moving this functionality to a more capable device is the sensible approach.

Appreciate the input.