I've tried implementing various containers and only some work. Why is that?
I have a hAP ax3 with an SSD connected via USB. Can run Pi Hole, nginx, and Trilium easily. However, containers like metube, openspeedtest, 13 ft ladder, and karakeep start then immediately stop running. The give the non-descriptive "container latest:latest exited, status: 255" error. Some of those are extremely basic and don't require envs. All work on a Raspberry Pi 4B, which is also arm64.
Maybe that containers contain some code that tries to connect to some devices in /dev or /proc or /sys that not Mikrotik Devices can provide.
I have not any experience with the containers i Mikrotik Devices.
But for more problem solving, like another containers can you get into them with a shell like "docker -it sh".
I can see in the docs you can get inside of it with /container/shell 0
Why is that?
Short answer: because it isn't running full-fat Docker Engine. Long answer…
To extend @tangent's point, and at a high-level... a lot of times you do need to explicitly set the cmd= as the default may not be correct or require some specific program/args to run.
I have openspeedtest container that runs from latest tag on ROS (ARM arch) without any additional env. variables added. Did you try to turn on logging option for container and see if something is logged on ROS from container (stdout)?
I also have hap ax3. I use arm64v8 images. Perhaps this is somehow related.
Thanks. Something like this is what I was looking for - -not that I understand it all.
The first paragraph reads:
The RouterOS container.npk feature is highly useful, but it is a custom development written in-house by MikroTik, not a copy of Docker Engine or any of the other server-grade container engines.1 Because of the stringent resource constraints on the bulk of MikroTik’s devices, it is exceptionally small, thus unavoidably very thinly featured compared to its big-boy competition.
Do you have better success with arm64 v8 images?