expensive lookups with fast local cache reads. The cache size can be configured by using the core.yaml property cacheSize. Alpine-based docker images Starting with v2.0, Hyperledger Fabric Docker images confer a role onto an identity. These Node OU roles are defined in the $FABRIC_CFG_PATH/msp/config.yaml file and contain a list of organizational units whose members are considered to be part of the organization When using the folder-based MSP structure, this is accomplished by enabling “Node OUs” in the config.yaml file which resides in the root of the MSP folder: NodeOUs: Enable: true ClientOUIdentifier:

expensive lookups with fast local cache reads. The cache size can be configured by using the core.yaml property cacheSize. 2.6 Alpine-based docker images Starting with v2.0, Hyperledger Fabric Docker confer a role onto an identity. These Node OU roles are defined in the $FABRIC_CFG_PATH/msp/config.yaml file and contain a list of organizational units whose members are considered to be part of the organization When using the folder-based MSP structure, this is accomplished by enabling “Node OUs” in the config.yaml file which resides in the root of the MSP folder: NodeOUs: Enable: true ClientOUIdentifier: Certificate:

expensive lookups with fast local cache reads. The cache size can be configured by using the core.yaml property cacheSize. Alpine-based docker images Starting with v2.0, Hyperledger Fabric Docker images confer a role onto an identity. These Node OU roles are defined in the $FABRIC_CFG_PATH/msp/config.yaml file and contain a list of organizational units whose members are considered to be part of the organization When using the folder-based MSP structure, this is accomplished by enabling “Node OUs” in the config.yaml file which resides in the root of the MSP folder: NodeOUs: Enable: true ClientOUIdentifier:

expensive lookups with fast local cache reads. The cache size can be configured by using the core.yaml property cacheSize. Alpine-based docker images Starting with v2.0, Hyperledger Fabric Docker images confer a role onto an identity. These Node OU roles are defined in the $FABRIC_CFG_PATH/msp/config.yaml file and contain a list of organizational units whose members are considered to be part of the organization When using the folder-based MSP structure, this is accomplished by enabling “Node OUs” in the config.yaml file which resides in the root of the MSP folder: NodeOUs: Enable: true ClientOUIdentifier:

expensive lookups with fast local cache reads. The cache size can be configured by using the core.yaml property cacheSize. Alpine-based docker images Starting with v2.0, Hyperledger Fabric Docker images confer a role onto an identity. These Node OU roles are defined in the $FABRIC_CFG_PATH/msp/config.yaml file and contain a list of organizational units whose members are considered to be part of the organization When using the folder-based MSP structure, this is accomplished by enabling “Node OUs” in the config.yaml file which resides in the root of the MSP folder: NodeOUs: Enable: true ClientOUIdentifier:

expensive lookups with fast local cache reads. The cache size can be configured by using the core.yaml property cacheSize. Alpine-based docker images Starting with v2.0, Hyperledger Fabric Docker images confer a role onto an identity. These Node OU roles are defined in the $FABRIC_CFG_PATH/msp/config.yaml file and contain a list of organizational units whose members are considered to be part of the organization When using the folder-based MSP structure, this is accomplished by enabling “Node OUs” in the config.yaml file which resides in the root of the MSP folder: NodeOUs: Enable: true ClientOUIdentifier:

expensive lookups with fast local cache reads. The cache size can be configured by using the core.yaml property cacheSize. 2.6 Alpine-based docker images Starting with v2.0, Hyperledger Fabric Docker confer a role onto an identity. These Node OU roles are defined in the $FABRIC_CFG_PATH/msp/config.yaml file and contain a list of organizational units whose members are considered to be part of the organization When using the folder-based MSP structure, this is accomplished by enabling “Node OUs” in the config.yaml file which resides in the root of the MSP folder: NodeOUs: Enable: true ClientOUIdentifier: Certificate:

the organization. • Organizational Units (OUs): These are listed in the $FABRIC_CFG_PATH/msp/config.yaml file and contain a list of organizational units, whose members are considered to be part of the organization -f - specify which docker-compose file use (defaults to ˓→docker-compose-cli.yaml) -s - the database backend to use: goleveldb (default) or couchdb -l - the chaincode CORE_LOGGING_LEVEL in the cli container is set to DEBUG. You can set this by modifying the docker-compose-cli.yaml file in the first-network directory. e.g. cli: container_name: cli image: hyperledger/fabric-tools:$IMAGE_TAG

the organization. Organizational Units (OUs): These are listed in the $FABRIC_CFG_PATH/msp/config.yaml file and contain a list of organizational units, whose members are considered to be part of the organization -f - specify which docker-compose file use (defaults to docker-compose-cli.yaml) -s - the database backend to use: goleveldb (default) or couchdb -l CORE_LOGGING_LEVEL in the cli container is set to DEBUG. You can set this by modifying the docker- compose-cli.yaml file in the first-network directory. e.g. cli: container_name: cli image: hyperledger/fabric-tools:$IMAGE_TAG

the organization. Organizational Units (OUs): These are listed in the $FABRIC_CFG_PATH/msp/config.yaml file and contain a list of organizational units, whose members are considered to be part of the organization -f - specify which docker-compose file use (defaults to docker-compose-cli.yaml) -s - the database backend to use: goleveldb (default) or couchdb -l CORE_LOGGING_LEVEL in the cli container is set to DEBUG. You can set this by modifying the docker- compose-cli.yaml file in the first-network directory. e.g. cli: container_name: cli image: hyperledger/fabric-tools:$IMAGE_TAG