CML docker version tagging

NPM is registering the versions properly, however DockerHub is not. Be able to pin the exact version if CML is important to warranty the reproducibility of the workflow. Changes in latest may break existing workflows and enforces us to work with backward compatibility

[hsharrison]

I brought this up her but was redirected here.

We would like to have a pinned version.

In the other issue I was asked what the pain point was, and it’s true that you all have not made any backwards incompatibilities. So the pain point is merely that we have policies about pinning images and not having versions forces us to break that policy and then explain a comment why it’s pinned latest, having team members get confused about this every now and then and think someone made a mistake (e.g. if they see cml:latest in the CI logs), etc.

Maybe there will never be a problem and nothing will ever be broken but it does take some “cognitive load” to remember why it’s not version pinned.

[DavidGOrtega]

@0x2b3bfa0 lets attack this definitely.

We have to tag with:

• CUDA 10 and 11
• Python 3
• DVC 2

Not sure about DVC

So the image could be

• dvcorg/cml:cuda10-python-dvc2:{version}
• dvcorg/cml:cuda11-python3-dvc:{version}

We can also for easiness and clarity get rid off elgohr/Publish-Docker-Github-Action. Has served us very well but for this might be easier for us to all without it like we are tagging later on.

We can do also #383

We should probably also freeze dvcorg/cml:latest or always stick with dvcorg/cml to be cuda 10.

@dmpetrov