securekey / fabric-examples

133 stars 58 forks source link

make example-network returns error #14

Open GingerMoon opened 5 years ago

GingerMoon commented 5 years ago

$ make example-network Service 'org1peer1' depends on service 'chaincoded' which is undefined. make: *** [Makefile:49: example-network] Error 1

maxrobot commented 5 years ago

@bstasyszyn do you have an update to this issue?

I have encountered it too.

I tried removing the dependency on chaincoded editing the docker-conpose.yaml as such:

    depends_on:
      - orderer1
      - builder
      - golangruntime
      # - chaincoded

this returns:

Recreating fabsdkgo_org2ca1_1       ... done
Recreating fabsdkgo_org1ca1_1       ... done
Recreating fabsdkgo_golangruntime_1 ... done
Recreating fabsdkgo_orderer1_1      ... done
Recreating fabsdkgo_builder_1       ... done
Recreating fabsdkgo_org1peer2_1     ... done
Recreating fabsdkgo_org2peer1_1     ... done
Recreating fabsdkgo_org1peer1_1     ... done
Recreating fabsdkgo_org2peer2_1     ... done
Attaching to fabsdkgo_org2ca1_1, fabsdkgo_orderer1_1, fabsdkgo_org1ca1_1, fabsdkgo_builder_1, fabsdkgo_golangruntime_1, fabsdkgo_org1peer2_1, fabsdkgo_org2peer2_1, fabsdkgo_org1peer1_1, fabsdkgo_org2peer1_1
org2ca1_1        | WARNING: no logs are available with the 'none' log driver
orderer1_1       | WARNING: no logs are available with the 'none' log driver
org1ca1_1        | WARNING: no logs are available with the 'none' log driver
fabsdkgo_org2ca1_1 exited with code 1
fabsdkgo_orderer1_1 exited with code 1
builder_1        | WARNING: no logs are available with the 'none' log driver
golangruntime_1  | WARNING: no logs are available with the 'none' log driver
org1peer2_1      | WARNING: no logs are available with the 'none' log driver
fabsdkgo_org1ca1_1 exited with code 1
org2peer2_1      | WARNING: no logs are available with the 'none' log driver
org1peer1_1      | WARNING: no logs are available with the 'none' log driver
fabsdkgo_org1peer2_1 exited with code 1
org2peer1_1      | WARNING: no logs are available with the 'none' log driver
fabsdkgo_org1peer1_1 exited with code 1
fabsdkgo_org2peer2_1 exited with code 1
fabsdkgo_org2peer1_1 exited with code 1

VERY BAD

additionally I attempted to launch linking the docker-compose-chaincoded.yaml as such:

$ docker-compose -f docker-compose.yaml -f docker-compose-chaincoded.yaml up

which gives the errors:

ERROR: for chaincoded  Cannot start service chaincoded: b'OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \\"/opt/gopath/src/github.com/hyperledger/fabric-sdk-go/test/scripts/chaincoded.sh\\": stat /opt/gopath/src/github.com/hyperledger/fabric-sdk-go/test/scripts/chaincoded.sh: no such file or directory": unknown'

Any ideas would be appreciated :)

bstasyszyn commented 5 years ago

Please try the latest code.

maxrobot commented 5 years ago

@bstasyszyn thank you very much for the fix, interestingly the certificate authorities still dies...

builder_1        | WARNING: no logs are available with the 'none' log driver
org2ca1_1        | WARNING: no logs are available with the 'none' log driver
org1ca1_1        | WARNING: no logs are available with the 'none' log driver
fabsdkgo_org2ca1_1 exited with code 1
fabsdkgo_org1ca1_1 exited with code 1
chaincoded_1     | Installing chaincodes ...
orderer1_1       | WARNING: no logs are available with the 'none' log driver
golangruntime_1  | WARNING: no logs are available with the 'none' log driver
org2peer1_1      | WARNING: no logs are available with the 'none' log driver
org1peer1_1      | WARNING: no logs are available with the 'none' log driver
org1peer2_1      | WARNING: no logs are available with the 'none' log driver
org2peer2_1      | WARNING: no logs are available with the 'none' log driver
chaincoded_1     | Running chaincoded ...

Any idea how one could fix this frightful issue?

bstasyszyn commented 5 years ago

@bstasyszyn thank you very much for the fix, interestingly the certificate authorities still dies...

builder_1        | WARNING: no logs are available with the 'none' log driver
org2ca1_1        | WARNING: no logs are available with the 'none' log driver
org1ca1_1        | WARNING: no logs are available with the 'none' log driver
fabsdkgo_org2ca1_1 exited with code 1
fabsdkgo_org1ca1_1 exited with code 1
chaincoded_1     | Installing chaincodes ...
orderer1_1       | WARNING: no logs are available with the 'none' log driver
golangruntime_1  | WARNING: no logs are available with the 'none' log driver
org2peer1_1      | WARNING: no logs are available with the 'none' log driver
org1peer1_1      | WARNING: no logs are available with the 'none' log driver
org1peer2_1      | WARNING: no logs are available with the 'none' log driver
org2peer2_1      | WARNING: no logs are available with the 'none' log driver
chaincoded_1     | Running chaincoded ...

Any idea how one could fix this frightful issue?

@maxrobot This issue should be fixed with the latest commit.

maxrobot commented 5 years ago

thank you very much :)