kitchen-docker Built container ID detection is not specific enough, and can match pip package installations

When installing pip packages in the provision_command while building container images, it can output something similar to Docker's final message with the container ID:

Successfully built ansible PyYAML pycrypto cryptography MarkupSafe pycparser

This will cause the container ID to be mistakenly identified as pycparser. The last instance of the matching message could be used to avoid such errors.

Nov 18 '16 14:11 danielkza

I just came across this, you can use the -qqq flag to suppress Pip's output as a quick fix.

Mar 25 '17 09:03 lobsterdore

I submitted a fix for this 9 months ago in #332 but seems that no maintainers are looking at PRs - @stuartpreston would you have a moment to take a look by any chance please?

Dec 19 '19 11:12 andyspiers

@andyspiers I don't have the rights to push gems into RubyGems on this driver I'm afraid. The owners of the gem are listed here: https://rubygems.org/gems/kitchen-docker - I think I've done as much as I can to help here.

Dec 19 '19 18:12 stuartpreston

Thanks for your response, Stuart. I'll try chasing one of the gem owners (after fixing the merge conflict which my PR has now developed :) )

Dec 19 '19 20:12 andyspiers