From 8bbdd0faf035ec89796dec142e98aa338c94246d Mon Sep 17 00:00:00 2001 From: Tatsuya Sato Date: Fri, 14 Jun 2019 21:23:53 +0000 Subject: [PATCH] [FAB-15716] Fix instructions for dev-mode This patch fixes the instructions for dev-mode. For the commands to start the chaincode to work properly, this patch modifies the commands. - Use peer.address flag (instead of the unused env var after FAB-14770) - Add CORE_PEER_TLS_ENABLED=false (dev-mode is for non-TLS mode only) FAB-15716 #done Signed-off-by: Tatsuya Sato Change-Id: I160d22389bb611c5b96ee880497266f06d25abd7 --- chaincode-docker-devmode/README.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/chaincode-docker-devmode/README.rst b/chaincode-docker-devmode/README.rst index aa57190b7f..c195edbb45 100644 --- a/chaincode-docker-devmode/README.rst +++ b/chaincode-docker-devmode/README.rst @@ -69,6 +69,8 @@ one for the chaincode environment and a CLI to interact with the chaincode. The commands for create and join channel are embedded in the CLI container, so we can jump immediately to the chaincode calls. +.. note:: TLS is not enabled as it is not supported when running chaincode in dev mode. + Terminal 2 - Build & start the chaincode ---------------------------------------- @@ -93,7 +95,7 @@ Now run the chaincode: .. code:: bash - CORE_PEER_ADDRESS=peer:7052 CORE_CHAINCODE_ID_NAME=mycc:0 ./abstore + CORE_CHAINCODE_ID_NAME=mycc:0 CORE_PEER_TLS_ENABLED=false ./abstore -peer.address peer:7052 The chaincode is started with peer and chaincode logs indicating successful registration with the peer. Note that at this stage the chaincode is not associated with any channel. This is done in subsequent steps