Hyperledger fabric installation - hyperledger-fabric

I have windows 7 machine and RHEL 6.0.
Can we install hyperledger fabric on Windowa 7 and RHEL 6.0 without using vagrant and docker.? If yea, please describe the steps.

Hyperledger Fabric does not deliver a complete set of binaries for all operating systems. There are native binaries for the various tools (configtxgen, cryptogen, configtxlator and peer) available for Windows, MacOSX, and Linux (for X86, ppc and s390 architectures). There are published Docker images for Ubuntu. Building Centos/RHEL images or binaries should be a straight-forward process, but is not presently a tested/supported configuration. The Node and Java SDKs should run just about anywhere.
It should also be noted that you cannot run without Docker, as chaincode is run in independent containers, managed by the peer. Hence, trying to avoid use of Docker is really a forgone conclusion - you cannot.

No.
Here are two walk throughs on how to do it.
https://developer.ibm.com/opentech/2016/07/21/running-hyperledger-fabric-natively-on-windows/
http://hyperledger-fabric.readthedocs.io/en/latest/dev-setup/devenv.html

Hyperledger Fabric 1.0.0 requires RHEL 7.3 or CentOS 7.3, gRPC has a dependency on the latest and greatest gnu C libraries.
Will not work on RHEL 6.0 !

Related

Error creating channel using testnetwork on Hyperledger Fabric

I am currently learning about hyperledger fabric, and am having issues creating channels on the testnetwork. I am on windows 10 and have the latest version of the fabric and docker.
When I run this command ./network.sh up createChannel in my git bash I get this error
Error on outputChannelCreateTx: could not generate default config template: error parsing configuration:
could not create application group: failed to create application org: 1 - Error loading MSP configuration
for org Org1MSP: could not load a valid ca certificate from directory
C:\fabric-samples\test-network\organizations\peerOrganizations\org1.example.com\msp\cacerts:
CreateFile C:\fabric-samples\test-network\organizations\peerOrganizations\org1.example.com\msp\cacerts:
The system cannot find the file specified.
+ res=1
Failed to generate channel configuration transaction...
Create channel failed
I am unsure as the source of this issue. Do I need to install the samples and binaries again? Is it where I'm running the commands?
I'm pretty sure that you will get more troubles cause you're using Windows 10. Even if you use git-bat (or
Cygwin like, etc), you should aware that most of script was written for linux (especially for ubuntu-based linux). Next step, when you work with chaincode-nodejs, it will install some required libraries, some only works on Linux OS. Please consider switching to Linux
P/s . I'm using ubuntu 20.04 LTS for Fabric 2.2. It works perfect.

error response from daemon container is not running

Im running ubuntu terminal 18.04 on window 10 Pro , Im getting error while running ./startFabric.sh
Error response from daemon: Container d827b753c3fda5ca92ada94c28e6362ebab32960f2af8805b4c9706e0056734d is not running
I have tried all the methods posted previously, can anyone please help me?
I tried removing all the container by using command docker ps -qa | xargs docker rm -f
https://i.imgur.com/NxxVyUn.png
Looks like you are trying to run the Hyperledger Composer simple fabric development server (which is basically a very simple hyperledger fabric environment to help you get started with composer using a hyperledger fabric network) inside a windows subsystem layer for linux environment. This isn't supported on Windows (either in git bash or in windows subsystem layer for linux).
If you are looking to use hyperledger composer then you should use a hypervisor to run a real linux VM such as virtualbox, vmware or hyperv (however it is highly recommended that you now invest time in the new programming models in hyperledger fabric rather than use hyperledger composer)
If you are looking to just using hyperledger fabric then you can start by looking at
https://hyperledger-fabric.readthedocs.io/en/release-1.4/install.html

Are there any limitations regarding the age of a linux distribution which can be used to create a docker base-image?

Im wondering if its possible to use very old Linux Distribution like Debian GNU/Linux 3.1 (Sarge) and create a base-image of it to run legacy code not working under "younger" distros.
Only Thing i found about it was somebody successfully using Ubuntu Feisty: Run old Linux release in a Docker container?
Are there any known limitations?
Your host needs to have a minimal version of the Linux kernel, and that version is 3.10
See
Docker minimum kernel version 3.8.13 or 3.10
extract from the previous link
There's also a shell-script to check if your system has the required dependencies in place and to check which features are available;
https://github.com/docker/docker/blob/master/contrib/check-config.sh
So you can use this to check if you will be able to use docker on this host.
From
https://wiki.debian.org/DebianSarge?action=show&redirect=Sarge
I see
kernel : linux 2.4.27 and 2.6.8
So it may not work

Hyperledger Fabric 1.0 Ubuntu 16.04 Setup issue

Following 2 links to setup Hyperledger Fabric 1.0 in system.
First link Hyperledger-fabric setup
After following commands
cd $GOPATH/src/github.com/hyperledger/fabric/devenv
vagrant up
vagrant ssh
Followed hypeledger latest setup docs
After using
cd $GOPATH/src/github.com/hyperledger/fabric
make dist-clean all
An error occured...
github.com/hyperledger/fabric/vendor/github.com/mattn/go-sqlite3 /usr/bin/ld: cannot find -lrocksdb collect2: error: ld returned 1 exit
status Makefile:137: recipe for target 'build/bin/peer' failed make:
*** [build/bin/peer] Error 2
On Left side my vagrant is running and right side is my Hyperledger Fabric 1.0 Setup command make dist-clean all
To me this seems to be problem of rocksdb, how can I resolve this?
Hyperledger Fabric 1.0 can be installed without having to build from source. The project publishes stable Docker images and binaries for each release. This may be a better approach to installing Fabric and its dependencies.
However, if you want to build from source, note that Vagrant is no longer needed. The build should be capable of running natively on most platforms (Mac, Windows and Ubuntu).
You will need the same prerequisites as for the Getting Started approach above - Docker (preferably the latest release), Go (1.9.x), Python 2.7 and Node 6.9.x (note that we do not yet support Node 7.x).
Occasionally, it has been observed that a fresh build (make all) from scratch may occasionally fail. If so, try running (make all) again.
As for the rocksdb error, Fabric no longer has a dependency on rocksdb and uses leveldb instead. It is entirely likely that because the vagrant environment gets little use of late, that it is not current.
I fond solution in one git hub link.
One can try to resolve this issue by using following commands-
apt-get install librocksdb-dev
apt-get install libsnappy-dev
apt-get install libbz2-dev
After this rockdb error should not be there. Will post more if found any other error and there solutions too.

Is it possible to build packages for multiple versions of Red hat Linux on a single server?

I have a set of programs for analyzing radiation data and I want to build packages for Red Hat Linux versions 4.x - 6.x. Is it possible to build these packages on a single build server running a single version of Red Hat Linux or do I need to build the version 4.x package on a server running version 4.x and the version 5.x package on a server running version 5.x?
If I can build packages for several versions on a single server, must that server be running the newest version or the oldest version of the OS?
You need to build toolchain for different OS environments (toolchain for Redhat 4.x and 5.x) and with in toolchain you can build packages for specific OS. toolchain is like a chroot environments.
You can create multiple Virtual machine using KVM and build many version of packages using single node..
You can use UML (User Mode Linux) which is quite interesting... Check out following Link
http://uml.devloop.org.uk/howto.html
You can build your packages in a chroot jail. You can use mach to do so.
Here's a tutorial on building packages with mach you could refer to, though it may be outdated.

Resources