But it's not that it won't work at all: $ docker run --rm -it alpine:latest /bin/sh Unable to find image 'alpine:latest' locally latest: Pulling from library/alpine df20fa9351a1: Already exists

Looks like that the user can not access docker endpoint and also cannot even create a file when the current directory is mounted to the container, you need to fix these permission errors first. I

Hi Bozhidar, Can you share the commands/output from when you packaged the chaincode? You may also find it helpful if you have not already done so, to review the tutorial “Deploying a Smart Contract

Tried. Doesn't work: (base) [user@f30 mywork]$ ./minifab up Unable to find image 'hfrd/minifab:latest' locally latest: Pulling from hfrd/minifab df20fa9351a1: Already exists 16d327ff9a88: Pull

Hello everyone. I got a problem with an 1.4.6 Fabric network with a network (27 peers and 5 orderers) where there is one peer (anchor peer) in an Organization that stopped commiting transactions. I

Hello All, The peer has joined the channel and chaincode is packed on. I have a problem with instantiating chaincode in Hyperledger fabric Network version 2: # peer lifecycle chaincode install

Hello - I do have a pegjs grammar for policies that could be useful. https://gist.github.com/mbwhite/b6f78b60bb9a2d407e7e623ca1e553cf Regards, Matthew. Matthew B White IBM Blockchain Solutions

Hi Everyone, I'm using Node.js Fabric SDK v1.4 for managing chaincode operations such as installing, instantiating, and upgrading. When to instantiate or upgrade a chaincode, I have to provide an

Try minifabric, only takes 5 minutes to know if it works for you or not.

I thought so too at first as I'm aware Fedora has a more restrictive security guideline. I installed firewalld and did according to the provided manual. It's different now, but still nothing

Hi Nathan, This is definitely possible. Chainstack customers are running production-grade Hyperledger Fabric 2.x networks in exactly three clouds you mentioned. Regards, Eugene Aseev

Reminder: Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 28 August 2020, 6:00am to 7:00am, (GMT+01:00)

Hi Nathan, As Jacov suggests you have to upgrade your network (ordering service, peers, etc) to 1.4.x (and then optionally to 2.x) in order to get the RAFT based HLF Ordering Service that can be

Looks like that the ports were fire-walled. Please see this doc https://github.com/litong01/minifabric/blob/master/docs/RunningOnFedora.md to get a solution on how to do this. Thanks. Tong Li IBM Open

This is getting weirder and weirder. I removed everything, tried to start from a clean build. Got this. (I have to say the peer might be there because I tried docker run hyperledger/fabric-peer - this

Can you do a `docker ps -a`, the containers are stopped, so a standard `docker ps` wont show them. Then share the logs from one of the exited containers, such as `docker logs peer0.org1.example.com`

I'm trying to get the Fabric-Samples running in Fedora 30. Strangely the docker containers always terminate right after starting them: (base) [user@f30 test-network]$ ./network.sh up Starting nodes

Nathan, It is possible and in fact used today. For example, MiPasa.org is using a Fabric network running with nodes on Oracle (using OBP), IBM, and Azure clouds. These are based on Fabric 1.4

It is possible only with 1.4.1+ as it hasRaft. You can deploy Raft orderers in differentcontinents and (or) on the moon, but you need to keep in mind that youcan't have TLS termination (proxies that

Dear Atsushi, For the question 1, my thought is to ensure we use external backup procedure before terminating peer1 and peer2. For the question 2 I wonder what is question bothering you since