Im trying to find a container for ARM64 ROS devices, that can run a web browser on it.
Basically so I can test site access from the router itself and do stuff like run a speedtest via speedtest.net directly on the router.
I work for a ISP and would like to use this on our breakouts.
I tried soooo many containers already and got close with a firefox container but it was so slow and just ended up crashing.
if you have any ideas or know of a web container I can run on a MIK. let me know.
I don't want workarounds like use a linux server. my constraints are this:
it must be in a mikrotik container on a mikrotik arm64 router. must be a web browser or a global speed test website like ookla (Speedtest.net). the router MUST host this no other device.
Containers are not virtual machines, they rely on the host device (RouterOS) for most things. They can't run browsers and other graphical tools. But you can already run "/tool fetch url=" on the router, to test connectivity from the router itself.
You could run a comnmand like tool like "speedtest-cli" that tests download speed from the speedtest.com server to your router. But running a browser is not the right thinking about the issue. You must think what specific tasks you need to accomplish and run tools that do them.
The container is running and RouterOS is doing it's job, but it looks like the developer of this container image has abandoned it and it does not work for other people either, see in the "Issues" section, there are other that say it's always "0.0" like yours: Fails on RB5009 with RoS 7.10.1 · Issue #1 · cdhtlr/MikroTik-Speedtest · GitHub
You can try other containers like "SpeedKetchup". Those will not have step by step instructions for MikroTik specifically though.
We are working on a much improved container experience, likely for RouterOS 7.22
Check if the container has a DNS resolver. From you screenshot, DNS is empty. Login to the container, with
/container print
/container shell 0
0 in this case is the index of the container as displayed by print, replace with the appropriate number. Then check
cat /etc/resolve.conf
To see whether the file has a line with nameserver xxx.xxx.xxx.xxx. If not try to set the DNS on the container setting and restart the container. Alternatively, edit /etc/resolve.conf in the container shell and add nameserver 8.8.8.8 or something similar.
Also, in case you want to programmatically do something with the result, you can run the speedtest program with -f json and it returns the result in JSON, that RouterOS can parse into array (with deserialize):
to see the correct number of the alpine container. 0 is probably you other container. But it's better that you give it a name, such as alpine and use the syntax from my previous screenshot:
