-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
Buenas. Usando el docker, desde un Debian 9 actualizado y con docker y docker-compose actualizados a ultimas versiones, tras ejecutar las instrucciones de https://github.com/blockchainempresarial/curso-hyperledger-fabric/tree/master/acme-network y tras eso ejecutar:
docker volume create portainer_data
docker run -d -p 8000:8000 -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer
CHANNEL_NAME=$CHANNEL_NAME docker-compose -f docker-compose-cli-couchdb.yaml up -d
docker exec -it cli peer channel create -o orderer.acme.com:7050 -c marketplace -f ./channel-artifacts/channel.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/acme.com/orderers/orderer.acme.com/msp/tlscacerts/tlsca.acme.com-cert.pem
Desde portainer veo que los peers y el oderer no levantan:
peer0.org1.acme.com | 2020-09-04 19:25:06.019 UTC [main] InitCmd -> ERRO 001 Cannot run peer because error when setting up MSP of type bccsp from directory /etc/hyperledger/fabric/msp: could not load a valid signer certificate from directory /etc/hyperledger/fabric/msp/signcerts: stat /etc/hyperledger/fabric/msp/signcerts: no such file or directory
Algo falla en este mapeo:
volumes:
- /var/run/:/host/var/run/
# ---CHANGED--- changed to reflect peer name, org name and our company's domain
- ../crypto-config/peerOrganizations/org1.acme.com/peers/peer0.org1.acme.com/msp:/etc/hyperledger/fabric/msp
Pero solo dentro del Ubuntu dockerizado me falla, porq desde mi Debian host anda. Algo de docker dentro de docker debe faltar o estar produciendo un bug.
Saludos
Metadata
Metadata
Assignees
Labels
No labels