Closed CodeMan99 closed 1 year ago
Thanks for reporting this. I wish I were more docker-savvy, looks like I'll have to revert the older commit, will do a bit of docker 101 first.
@Treehopper your PR #679 forces the use of --entrypoint
on the command line. Is there a way to achieve what you need on Windows without removing the ENTRYPOINT
definition in Dockerfile
?
@Treehopper hope to hear from you soon. I'll revert the commit in your PR this weekend if there's no work-around.
I updated the images at docker.io.
It looks like the 1.96 tag was replaced by a newer image after this PR was merged. In the future, could you please push a new version tag instead of overwriting existing tags? This broke some of our CI builds and we had to revert to 1.94. Thanks, and keep up the good work! 👍 🙏
@nre-ableton sorry about that! I think I've made about every possible mistake with Docker there is to make. (Actually, when I think about it I'm probably underestimating myself there.) At least this particular mistake won't be repeated.
@AlDanial It's no problem, as I said, we have a workaround in place. Just something to keep in mind for future releases!
@AlDanial hey, I it seems like the "latest" tagged image was not overwritten. Therefore the bug still persists when pulling aldanial/cloc.
@gute-kunst I just re-pushed latest
, let me know if you're not getting 1.96 from that.
Describe the bug
This seems to stem from the change to drop
ENTRYPOINT
and instead useCMD
. The following works as expected.