Currently, chain-cli used fablo version 2.0.0:
Latest available in the npm registry is 2.2.0:
https://www.npmjs.com/package/fablo
Latest underlying fablo version is 2.4.2:
https://github.com/hyperledger-labs/fablo/releases
Recently a few previously-working development environments broke after routine Linux operating system updates.
Installing chaincode basic-asset...
CHAINCODE_VERSION: 0.0.1
PEER_ADDRESS: peer0.curator.local:7041
CA_CERT: crypto-orderer/tlsca.orderer.local-cert.pem
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image build failed: write unix @->/run/docker.sock: write: broken pipe
Error: Command failed: "test-network/fablo" "up"
I found that downgrading Docker from v29.x to v28.x resolved the issue:
sudo apt install docker-ce=5:28.5.2-1~debian.12~bookworm
For now, that's a short term fix, documented in this issue in case it helps others.
Longer term, we'll want to get this dependency updated.
I did some brief testing and I believe this will require some changes in how the chain-cli packages uses fablo or how it generates the configuration files used by fablo.
Currently,
chain-cliusedfabloversion2.0.0:sdk/chain-cli/package.json
Line 23 in eb6050f
Latest available in the npm registry is
2.2.0:https://www.npmjs.com/package/fablo
Latest underlying
fabloversion is2.4.2:https://github.com/hyperledger-labs/fablo/releases
Recently a few previously-working development environments broke after routine Linux operating system updates.
I found that downgrading Docker from v29.x to v28.x resolved the issue:
sudo apt install docker-ce=5:28.5.2-1~debian.12~bookwormFor now, that's a short term fix, documented in this issue in case it helps others.
Longer term, we'll want to get this dependency updated.
I did some brief testing and I believe this will require some changes in how the
chain-clipackages usesfabloor how it generates the configuration files used byfablo.