CMD and ENTRYPOINT

[alexei-led]

I think that moving CMD and ENTRYPOINT from their standard place in Dockerfile to LABEL looks unnatural.
Think about what problem do you want to solve?
tagbot run can do a second run without problem, inspecting previously run containers and getting CMD and ENTRYPOINT from them.
tugbot watch should be smart enough to detect test container run and get test results from it: watching mounted volume or copying after run.
I would like to keep "adoption learning curve" as low as possible: know how to deploy and run container? Just add couple labels to mark test container, point to test results and "subscribe" to events and you've done - tagbot will run tests on events and will collect all test results continuously.

[shayts7]

You are porbably right. I wish docker had some notion of putting the docker run command next to an image, so when someone (like tugbot run for instance) would like to run the image he will know how to do it.