macs2 container: simplify name & tag

[kelly-sovacool]

https://github.com/CCBR/Dockers/tree/master/chipseq/ccbr_macs2_2.1.1.20160309

Can we change the name to just ccbr_macs2 and use semantic versioning for the tag?

Also, do we need the ccbr_ prefix in the container names since they're all part of the CCBR Github / nciccbr DockerHub?

[kopardev]

I remember having discussion about this in the past ... The convention we ended up with is: <org_account>/ccbr_<tool_name>_<tool_version>:v<docker_major_version_only>:

• <org_account>: This is nciccbr in most cases and cannot be changed as dockerhub lets us have only one org for our current account.
• ccbr_: prefix for all dockers we make
• <tool_name>: has to be lower case even in case of tools like "MACS2" as dockerhub requires everything to be in lowercase
• <tool_version>: we can host multiple version of the same tool and the version number needs to be clear in the docker URL itself.
• v: prefix to docker version ... no real reason to add this ... but following tradition here.
• <docker_major_version_only>: This is simply incremented the next time you re-build a docker with the same version of the tool ... eg. using a newer version of the base image

I hope that makes sense.... Comments welcome.

[kelly-sovacool]

I was thinking the tool_version seems to make the docker path a bit long / harder to read. If we do a good job of documenting which tags use which software versions, then it wouldn't be necessary to include tool_version -- users can just use the exact tag they need. There could also be cases of needing different combinations of software versions and we could have different tags covering those cases, again rather than having it encoded in the container name.