summaryrefslogtreecommitdiff
path: root/gluster-client
AgeCommit message (Collapse)Author
2018-03-01fix bug when multiple shell commands are specified in RUNRaghavendra Talur
If RUN is followed by two commands only the return value of second determines whether RUN was successful or not. This may lead to cases where docker build succeeds even when it should not. For example RUN /bin/false; /bin/true would be considered a success. Important thing to consider is that all yum/dnf commands should perform clean in the same RUN operation if we wish to keep the container image size small. Running clean in a second RUN operation leads to bigger image size contrary to expectation because each operation leads to a layer in the image. With the above two points considered, I have replaced ";" with "&&" where necessary and split a single RUN operation to two or many operations in other places. Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
2017-05-25Cleaning up RUN in dockerfileMohamed Ashiq Liyazudeen
This reduces the image size as it reduces the number of intermediate layers. Signed-off-by: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
2017-05-08Cleanup for the Unit testsMohamed Ashiq Liyazudeen
Signed-off-by: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
2016-10-28Gluster Client container Dockerfilehchiramm
Signed-off-by: hchiramm <hchiramm@redhat.com>