summaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorRaghavendra Talur <rtalur@redhat.com>2018-03-01 12:29:53 +0530
committerRaghavendra Talur <rtalur@redhat.com>2018-03-01 12:41:01 +0530
commitd7e7fb48f5f50c8fedc7228a3f4c13f324064274 (patch)
treeda24521fd402e73d7c00dff78f9e99dc876255f7 /README.md
parent697965ec5f1a51eaf11c2c4ac7f8e3e7e36d0e5b (diff)
downloadgluster-d7e7fb48f5f50c8fedc7228a3f4c13f324064274.tar.gz
gluster-d7e7fb48f5f50c8fedc7228a3f4c13f324064274.tar.bz2
gluster-d7e7fb48f5f50c8fedc7228a3f4c13f324064274.tar.xz
gluster-d7e7fb48f5f50c8fedc7228a3f4c13f324064274.zip
fix bug when multiple shell commands are specified in RUN
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>
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions