Deploying chaincode to peers

[nkaramolegos]

Hello, If the peers are running to docker containers how the akc-admin-go tool is aware where to install the chaincode? I mean in which docker container is the peer running

[eledra89]

The akc-admin-go is deprecated though. Please use this one instead: https://github.com/Akachain/akc-admin

For your question, the admin tool interacts directly with peers, it doesn't interact with the chaincode containers. If peers are running in docker, they will automatically create new docker containers that run the chaincode. So you will see both: peer and chaincode docker containers running.

There is a caveat though, if the peer is running in a Kubernetes Cluster, the chaincode still runs in a separated docker container, but it won't be controlled by Kubernetes. You will have to find it with docker ps rather than using Kube CLI.

in Fabric 2.x, there is the "external chaincode" where you can actually deploy your own chaincode container separately.

[nkaramolegos]

Can I ask why this tool is deprecated? Also, I didn't understand how this tool is interacting with the peers (not only for the chaincode). For example if a peer have to join a channel how this tools know the connection parameters to the peer (i.e in which container the peer in running)?

[nkaramolegos]

Any answer about the deprecation? I have seen that akc-admin use the bash for the administration. Is this a good approach? I thought SDK is better

[eledra89]

Extremely sorry for the late answer, I think I missed the notification as we r focusing on another project at the moment. This tool is deprecated because the person who wrote it moved to another company before even finishing it. It has not been tested on production yet. I can't recommend it to you. The NodeJS tool is the one we use daily in all environment (dev, test, staging, prod). We ran more than 10 projects, each has 3-4 environments (including production) so you can be sure that the akc-admin tool I referenced above should work properly

The Tool use Fabric SDK to interact with the peer. So you will need to give it access to all the channel artifacts and configuration files the Fabric SDK needs.