- Chaincode Upgrade Docker Container Environment
Re: Chaincode Upgrade Docker Container Environment
Brett T Logan <brett.t.logan@...>
toggle quoted messageShow quoted text
In core.yaml you can specify your own chaincode runtime image for golang, Java or Node. So you can extend the image to include your tools, publish the image to a Docker registry and then use that as the runtime in your core.yaml:
Software Engineer, IBM Blockchain
----- Original message -----
From: "Kimheng SOK" <sok.kimheng@...>
Sent by: fabric@...
Subject: [EXTERNAL] [Hyperledger Fabric] Chaincode Upgrade Docker Container Environment
Date: Fri, Jan 24, 2020 10:17 AM
I have one question, each time we upgrade our chaincode a new docker container is created.
But the problem is it doesn't inherit all the environment of the old version docker, from example if we install some program in the chaincode docker container, when we upgrade chaincode we need to install those program again in the new chaincode container.
Is there a solution, so that we don't need to re-install the program again and again when we upgrade our chaincode?
Join firstname.lastname@example.org to automatically receive all group messages.