Startup Error of Fabric Sequencer Example on OSX

Hey, I’m trying to startup daml-on-fabric using Canton. In particular, I’m starting a single sequencer up using:

CANTON_VERSION=0.18.2 COMPOSE_PROJECT_NAME="fabric-sequencer" docker-compose up

However, the sequencer fails to start with the following error:

peer0.org1.example.com_1  | 2020-10-12 12:30:37.548 UTC [comm.grpc.server] 1 -> INFO 03d unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.pee$
_address=172.23.0.5:60634 grpc.code=OK grpc.call_duration=2.5314ms
fabric.sequencer_1        | Org going to approve chaincode definition for my org.
fabric.sequencer_1        | Caught an exception running Channel mainchannel
fabric.sequencer_1        | org.hyperledger.fabric.sdk.exception.InvalidArgumentException: The packageId parameter can not be null or empty.

Any clue? I’m using MacOSX.

2 Likes

This is likely a recent problem that typically accompanies this error line:

Failed chaincode installation on peer peer0 grpcs://localhost:10051. Exhausted attempts. (5 of 5). Response: failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/dev-peer0.org1.example.com-sequencer-3c192c4930102b7fb06dff7a7ed57576168680cc250fa310baf82c6b7a4fa7c2-ba6e0367492daf5b7506cbc79dd55b5d81888b6438855ea249d874170364f94a/json": dial unix /host/var/run/docker.sock: connect: no such file or directory

This problem is caused by a newer version of Docker Desktop for macOS as explained in https://hyperledger-fabric.readthedocs.io/_/downloads/en/release-2.0/pdf/

This problem is caused by a newer version of Docker Desktop for macOS. To resolve this issue, in the Docker Desktop preferences, uncheck the box Use gRPC FUSE for file sharing to use the legacy osxfs file
sharing instead and click Apply & Restart.

1 Like

Oh boy. That indeed has fixed it. Thanks!