News for hackers. Stuff that matters.
Re:Testing with Jenkins, Ansible and Docker by SeoxyS on Friday April 11, 2014 @02:31PM (#7574590)
You should optimize your RUN commands. Every time you RUN in a Dockerfile, it creates a new filesystem layer. There's a hard limit (42, iirc) to the number of layers that Docker can support.

Instead of doing:

    RUN echo bar >> foo
    RUN echo baz >> foo
You could do:

    RUN echo bar >> foo \
        echo baz >> foo
Re:Testing with Jenkins, Ansible and Docker by 1331 on Friday April 11, 2014 @05:58PM (#7575853)
In my humble opinion, each layer should have a clear purpose: http://www.extellisys.com/articles/docker-layer-overload
Re:Testing with Jenkins, Ansible and Docker by shykes on Saturday April 12, 2014 @12:04AM (#7576929)
You make good points in this post. We are working on addressing some of them already. I would love to discuss this directly, you can ping me anytime, shykes on #docker / freenode.
Re:Testing with Jenkins, Ansible and Docker by jhspaybar on Friday April 11, 2014 @03:21PM (#7574912)
This limit is now higher(somewhere in the range of 100), and will eventually go away. Once this limit is gone, best practices will almost surely be one command per run.
Re:Testing with Jenkins, Ansible and Docker by jafaku on Friday April 11, 2014 @06:43PM (#7576035)
> Once this limit is gone, best practices will almost surely be one command per run.

Agreed, I thought the same, but then I hit the 127 (I think) limit.