You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The external chaincode launcher was added as part of the v2.0.0 release. This change allows users to break free of the dependency on the docker daemon inside the peer.
In particular users can launch chaincode as standalone servers, they can launch docker containers out of band running chaincode and connect to them, or they can launch separate kubernetes pods running the chaincode.
This encapsulates two test scenarios:
Launching the chaincode in Docker out of band and connecting to it
Launching the chaincode as a separate pod and connecting to it
We can make use of some tool such as microk8s to run the tests in CI: https://microk8s.io/
The text was updated successfully, but these errors were encountered:
The external chaincode launcher was added as part of the v2.0.0 release. This change allows users to break free of the dependency on the docker daemon inside the peer.
In particular users can launch chaincode as standalone servers, they can launch docker containers out of band running chaincode and connect to them, or they can launch separate kubernetes pods running the chaincode.
This encapsulates two test scenarios:
We can make use of some tool such as microk8s to run the tests in CI: https://microk8s.io/
The text was updated successfully, but these errors were encountered: