Docker image is named 'latest' and it should be 'openspeedtest' #30
Description
Docker images are usually referenced as org/image:tag, with org/image:latest being the latest version of the image. For example, if Google were to have an image called Gmail, then the image would be named google/gmail.
In OpenSpeedTest's case, the image is currently called latest, which doesn't make sense. It implies that the application is called 'latest', when in actual fact, the application is called 'openspeedtest'.
This caught me out and I'm an experienced Docker user. I'm sure it's caught others out, too (for example: #18) and especially those who are just getting started with Docker.
It gets even more confusing when someone wants to lock their deployment to a specific version. With the current image name, they would:
docker run ... openspeedtest/latest:v2.0.5 # Is is the latest version I'm running here? Or is it v2.0.5?
Looking at that command, it looks like I'm running the latest version, but I'm not...
The standard solution is to name the image openspeedtest/openspeedtest, then to users would run which version they wanted to in an expected way:
docker run ... openspeedtest/openspeedtest
docker run ... openspeedtest/openspeedtest:latest
docker run ... openspeedtest/openspeedtest:v2.0.5
I understand that it's suboptimal having 'openspeedtest' essentially duplicated, but this is pretty common in the open source world of Docker images.