readme changes to 1.0.3

sampleconfig/configs-explanation.md

@@ -22,7 +22,7 @@
 
 	```
 	name: cryptogen
-		image: ibmblockchain/fabric-tools:1.0.1
+		image: ibmblockchain/fabric-tools:1.0.3
 		imagePullPolicy: Always
 		command: ["sh", "-c", "cryptogen generate --config /sampleconfig/crypto-config.yaml && cp -r crypto-config /shared/ && for file in $(find /shared/ -iname *_sk); do dir=$(dirname $file); mv ${dir /*_sk ${dir}/key.pem; done && find /shared -type d | xargs chmod a+rx &&  find /shared -type f | xargs chmod a+r && touch /shared/status_cryptogen_complete "]
 		volumeMounts:
@@ -42,7 +42,7 @@
 	From kubernetes point of view, in the utils pods, a container named `configtxgen` is defined which uses the same command as described above to generate orderer genesis block. Here is the block from [blockchain.yaml](../../kube-configs/blockchain.yaml)
 	```
 	name: configtxgen
-		image: ibmblockchain/fabric-tools:1.0.1
+		image: ibmblockchain/fabric-tools:1.0.3
 		imagePullPolicy: Always
 		command: ["sh", "-c", "sleep 1 && while [ ! -f /shared/status_cryptogen_complete ]; do echo Waiting for cryptogen; sleep 1; done; cp /sampleconfig/configtx.yaml 	/shared/configtx.yaml; cd /shared/; configtxgen -profile TwoOrgsOrdererGenesis -outputBlock orderer.block && find /shared -type d | xargs chmod a+rx && find /shared -type f | xargs chmod a+r && touch /shared/status_configtxgen_complete && rm /shared/status_cryptogen_complete"]
 		env: