It's also possible you pulled the images before (maybe when doing byfn). Since we tag them as latest, if you already had latest images that exist, pulling new images would be skipped, run: docker rmi

Can you clean up your docker images and retry, the output is saying the binary inside your "fabric-tools:latest" image is 1.4.6, presumably at some point (probably byfn) tagged another version as late

Are you doing a `docker ps -a` presumably its crashed, `docker ps` only shows running containers Brett Logan Software Engineer, IBM Blockchain Phone: 1-984-242-6890 E-mail: brett.t.logan@...

Generally you implement some other standard. In particular the global supply chain standard is GS1. Items have what is called a GTIN identifying their category specific to your company and serial numb

Do your suppliers really need to operate their own Peers? If so, why? Can not you, and/or independent third parties operate the network and provide API's for your suppliers to submit data? Then you ne

The block files can be found in /var/hyperledger/production/ledgersData Brett Logan Software Engineer, IBM Blockchain Phone: 1-984-242-6890 E-mail: brett.t.logan@...

I'm not sure I understand the use case. If you have some transaction that the other members on your channel should in no way be party to or have knowledge of, you should have a separate channel on whi

While not a "known" issue, there was a likelihood that 2.0 changes broke devmode. We have an open item to test it amongst the dev team, and if not easily fixable to disable the codepath. Brett Logan S

Here is a very, very basic program to ingest the chaincode package and output a tarball of it: https://github.com/yeasy/blockchain_guide/blob/master/_code/unpack_chaincode.go Credit to Baohua Yang for

We expect sometime mid-year to announce Fabric 2.x as LTS. Once this happens there will be a period of time where both 1.4.4 and 2.x are LTS to provide a transition period for users to migrate to 2.x.

In 2.0 Fabric we added logic to remove unreferenced chaincode containers, so once your old version is no longer used anywhere it would be cleaned up. We also introduced a new chaincode builder and lau

The ordering services job is to assemble blocks from transactions and determine the final order of the transactions. It doesn't participate in the validation of the endorsed transactions. Once the ord

Part of the chaincode instantiation process is to compile the JAR, this isn't something you can hijack in 1.4.x without modifying the source code. Fabric v2.0 (which released last week) provides a fra

In core.yaml you can specify your own chaincode runtime image for golang, Java or Node. So you can extend the image to include your tools, publish the image to a Docker registry and then use that as t

As we close out the migration of Hyperledger Fabric and its supporting projects off of Gerrit and Jenkins to GitHub and Azure Pipeline's, our final task was to retire the use of Nexus for serving non-

What version of golang are you using? We recently added support for TLS1.3 and I assume the version of Go you are using doesn't support it. Brett Suhan Sumeet --- [EXTERNAL] [Hyperledger Fabric] Fabri

I'll add, anyone is welcome to submit the cherry-pick, keeping up with doc changes is no easy task :) Anoop Vijayan --- [EXTERNAL] Re: [Hyperledger Fabric] Adding org to existing network fails with mi

What do we need to do to make this an official vote and relax the rules? It would be nice to have this changed before the holiday's really get going. It's going to be harder than ever over the next mo

We could gate the DocBuild, UT and IT behind the success of VerifyBuild like we do today, and can set variables (BuildDoc and RunTests) as true or false and make them the conditions on which the DocBu

Hello Contributors, The time has finally come. The Hyperledger Fabric maintainers are planning for a migration of the core Fabric repository to GitHub this Friday morning Eastern Standard Time. We are