bug fixes. v2.2 is the first long-term support (LTS) release of Fabric v2.x. Fixes will be provided on the v2.2.x release stream until after the next LTS release is announced. Let’s take a look at some to the latest release from the previous release as well as from the most recent long term support (LTS) release. 2. Upgrading your components. Components should be upgraded to the latest version before to the newest release from the previous release as well as from the most recent long term support (LTS) release. Upgrading from 2.1 to 2.2 The 2.1 and 2.2 releases of Fabric are stabilization releases

bug fixes. v2.2 is the first long-term support (LTS) release of Fabric v2.x. Fixes will be provided on the v2.2.x release stream until after the next LTS release is announced. Let’s take a look at some to the latest release from the previous release as well as from the most recent long term support (LTS) release. 2. Upgrading your components. Components should be upgraded to the latest version before to the newest release from the previous release as well as from the most recent long term support (LTS) release. 10.1.1 Upgrading from 2.1 to 2.2 The 2.1 and 2.2 releases of Fabric are stabilization releases

to the latest release from the previous release as well as from the most recent long term support (LTS) release. 2. Upgrading your components. Components should be upgraded to the latest version before to the newest release from the previous release as well as from the most recent long term support (LTS) release. Upgrading from 2.0 to 2.1 The 2.1 release of Fabric is a stabilization release, featuring (substitute 2.1 for 2.0 in these commands if you are upgrading to that binary version from the 1.4.x LTS): docker run --rm -v /opt/backup/$PEER_CONTAINER/:/var/hyperledger/production/ \ -v

to the latest release from the previous release as well as from the most recent long term support (LTS) release. 2. Upgrading your components. Components should be upgraded to the latest version before to the newest release from the previous release as well as from the most recent long term support (LTS) release. 10.1.1 Upgrading from 2.0 to 2.1 The 2.1 release of Fabric is a stabilization release, (substitute 2.1 for 2.0 in these commands if you are upgrading to that binary version from the 1.4.x LTS): docker run --rm -v /opt/backup/$PEER_CONTAINER/:/var/hyperledger/production/ \ -v /opt/msp/:/et

Ubuntu $ cat /etc/os-release $ NAME="Ubuntu" $ VERSION="16.04.1 LTS (Xenial Xerus)" $ ID=ubuntu $ ID_LIKE=debian $ PRETTY_NAME="Ubuntu 16.04.1 LTS" $ VERSION_ID="16.04" $ HOME_URL="http://www.ubuntu.com/" /etc/apt/sources.list.old 2. 修改source.list sudo vim /etc/apt/source.list 添加以下信息 # deb cdrom:[Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1)]/ xenial main restricted deb-src http://archive.ubuntu

to the latest release from the previous release as well as from the most recent long term support (LTS) release. 2. Upgrading your components. Components should be upgraded to the latest version before to the newest release from the previous release as well as from the most recent long term support (LTS) release. 10.1.1 Upgrading from 2.0 to 2.1 The 2.1 release of Fabric is a stabilization release, (substitute 2.1 for 2.0 in these commands if you are upgrading to that binary version from the 1.4.x LTS): docker run --rm -v /opt/backup/$PEER_CONTAINER/:/var/hyperledger/production/ \ -v /opt/msp/:/et

to the latest release from the previous release as well as from the most recent long term support (LTS) release. 2. Upgrading your components. Components should be upgraded to the latest version before to the newest release from the previous release as well as from the most recent long term support (LTS) release. Upgrading from 2.0 to 2.1 The 2.1 release of Fabric is a stabilization release, featuring (substitute 2.1 for 2.0 in these commands if you are upgrading to that binary version from the 1.4.x LTS): docker run --rm -v /opt/backup/$PEER_CONTAINER/:/var/hyperledger/production/ \ -v

to the latest release from the previous release as well as from the most recent long term support (LTS) release. 2. Upgrading your components. Components should be upgraded to the latest version before to the newest release from the previous release as well as from the most recent long term support (LTS) release. 10.1.1 Upgrading from 2.1 to 2.2 The 2.1 and 2.2 releases of Fabric are stabilization releases (substitute 2.1 for 2.0 in these commands if you are upgrading to that binary version from the 1.4.x LTS): docker run --rm -v /opt/backup/$PEER_CONTAINER/:/var/hyperledger/production/ \ -v /opt/msp/:/et

to the latest release from the previous release as well as from the most recent long term support (LTS) release. 2. Upgrading your components. Components should be upgraded to the latest version before to the newest release from the previous release as well as from the most recent long term support (LTS) release. Upgrading from 2.1 to 2.2 The 2.1 and 2.2 releases of Fabric are stabilization releases (substitute 2.1 for 2.0 in these commands if you are upgrading to that binary version from the 1.4.x LTS): docker run --rm -v /opt/backup/$PEER_CONTAINER/:/var/hyperledger/production/ \ -v

JavaScript runtime that you can use to run applications and smart contracts. You are recommended to use the LTS (Long Term Support) version of node. Install node here [https://nodejs.org/en/]. Docker [https://www releases [https://github.com/hyperledger/fabric#releases]). At any given time, there will be a stable LTS (long term support) release branch, as well as the master branch for upcoming new features. Follow