FROM alpine:latest AS build
RUN wget -O speedtest.tgz \
	"https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-aarch64.tgz" \
	&& tar zxvf speedtest.tgz \
	&& chmod +x speedtest && chown root:root speedtest
RUN rm speedtest.tgz
RUN wget https://curl.se/ca/cacert.pem

From scratch
COPY --from=build /speedtest /bin/
COPY --from=build /cacert.pem /

ENTRYPOINT ["/bin/speedtest", "--accept-license"]
CMD [ "--ca-certificate=/cacert.pem" ]

11:17:03 container,info,debug Speedtest by Ookla
11:17:03 container,info,debug Server: Bell Canada - ABCD (id: 12345)
11:17:03 container,info,debug ISP: Bell Canada
11:17:03 container,info,debug Idle Latency: 1.00 ms (jitter: 0.23ms, low: 0.98ms, high: 1.84ms)
11:17:08 container,info,debug r Download: 1610.22 Mbps (data used: 727.5 MB)
11:17:08 container,info,debug 4.63 ms (jitter: 0.39ms, low: 2.96ms, high: 6.66ms)
11:17:18 container,info,debug r Upload: 1015.11 Mbps (data used: 1.2 GB)
11:17:18 container,info,debug 13.60 ms (jitter: 1.53ms, low: 3.69ms, high: 24.74ms)
11:17:18 container,info,debug Packet Loss: 0.0%
11:17:18 container,info,debug Result URL: https://www.speedtest.net/result/c/xyz

• Mine builds for all four major platforms rather than hard-code aarch64.
• I unpack the client tarball on the fly to extract the single static binary I want, letting the rest of the contents go to the bit bucket. Keep in mind that with a 2-stage build like this, that isn't strictly necessary, nor is your "rm speedtest.tgz" step. Everything from the first stage goes away in the second stage, so you can leave the first stage as messy as you like.
• I get the CA certificate bundle from Alpine rather than copy it in redundantly from the curl folk.
• You don't need all that dancing about with chmod and chown. The tarball has the executable marked properly, and the COPY step from the build stage to the final "FROM scratch" stage resets the permissions to root.
• The default operation mode for the CLI tool assumes you're running it interactively on a terminal, but under RouterOS, you can't see the cutesy ASCII art animations, so I disabled them.
• I split the flags between ENTRYPOINT and CMD differently, with the intent of separating those presumed to be unchanging from those likely to be overridden. The CA cert setting step belongs to ENTRYPOINT, IMHO, not to CMD. This allows one to set cmd="--format=json" to allow easy consumption of the results by another script watching rsyslog.

I found a lot to improve in that container, resulting in a new section on my MikroTik Solutions site, here. Here's what I changed/improved:

To accept the message please run speedtest interactively or use the following: 
    speedtest --accept-gdpr

Try it again; I've added that flag to the command line.

Try it again; I've added that flag to the command line.

It doesn't demand that here, but perhaps it skips that when it doesn't detect that you are in the EU.

  --server SERVER       Specify a server ID to test against. Can be supplied
                        multiple times
  --exclude EXCLUDE     Exclude a server from selection. Can be supplied
                        multiple times
  --json                Suppress verbose output, only show basic information
                        in JSON format. Speeds listed in bit/s and not
                        affected by --bytes

Is it possible to use ENV in mikrotik container solution to bypass parameters to the speedtest-call in your container.

For a single parameter:

Code: Select all

/container
  add remote-image=tangentsoft/speedtest-cli:latest \
  interface=veth1 cmd="--json" logging=yes