I try to initialize Fabric CA server by command:
./fabric-ca-server init -b {user}:{password}
and receive:
./fabric-ca-server: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ./fabric-ca-server)
I read that updating of GLIBC_2.28 is risky.
Help me please.
fabric-ca-server binaries are built on Ubuntu. The version of Ubuntu that was used will depend on the version of fabric-ca-server you are trying to use.
Whatever version of fabric-ca-server you are trying to run it won't run on your version of linux due fabric-ca-server now requiring a specific capability that is in GLIBC_2.28 or higher.
If you need a specific version of fabric-ca-server running on a specific distribution and version of linux you will need to clone the github repo for fabric-ca (checkout the appropriate tag for the version you want) and build the code yourself with the correct version of the GoLang compiler and other dependencies.
Related
I'm trying to upgrade Jfrog artifactory from 6.4.1 version to the latest 7.x version.
I'm not able to find the upgrade path in the manual.
Is there an official document on the upgrade path for the same?
The document that you referred is the correct document for the upgrade process.
I belive you are referring to Artifactory installed path. If yes, the default path would be /opt/jfrog/artifactory/. If it is zip installation in linux, there is a possibility that you might have installed in your own path. You can find the path below command in linux.
ps -ef | grep artifactory
If it is windows, you can open services and get the installed path of Artifactory. Later perform an upgrade.
Please be informed, that first you need to upgrade from 6.4.1 to 6.10 as there are some breaking changes. Later you can perform an upgrade to 7.x version. Depending on the installation type, you can follow the upgrade steps mentioned in the same document.
For version below 6.10.x, first upgrade to 6.10.x and then upgrade to the version that is mentioned in the upgrade document.
I am building a sample application in which I need to use Node Version v9.11.2 and npm 4.0.0. Currently I have Node Version v16.4.0 installed on my system. I tried to install the specific version by uninstalling the latest version and installing version 9.11.2 from official website
Problem: The problem is I can uninstall the latest version without any problem but when I try to install older version(9.11.2) the command gets opened and it does nothing. I also tried to install the older version using cli commands ie. npm install -g node#9.11.2, it installs the version but on checking the version using node -v, it still shows the latest version(16.4.0)
Below are the screenshots for better understanding
Installed version 9.11.2 but showing 16.4.0
Any Solution please ?
Is using docker a possibility? If so you can simply get a docker image of the required version and use if from there.
Another way is to use NVM which is a really useful tool to manage nodejs versions. I'm including their github repo for your convenience:
https://github.com/nvm-sh/nvm
A good option is to use NVM: https://github.com/coreybutler/nvm-windows (Windows) or https://github.com/nvm-sh/nvm (unix, macOS). With NVM you can enable different versions of node on the same machine and switch from one to another, usually it takes care of managing the installed packages and adding them to its own management system.
I am quite new to NodeJS and am planning to upgrade NodeJS version for my current project. The most recent NodeJS LTS is installed using NVM.
I need to keep switching between the current LTS that i am using and the new LTS that has been installed. I understand that i can do 'NVM use' for this purpose. npm-shrinkwrap.json is being used to lock down the npm package dependencies.
I am planning to follow the below approach both in my dev machine and build machine;
Is it okay? If not, please suggest a best approach.
nvm use latest_LTS
Update the package.json to pick the version which is supported by
latest_LTS
npm install
generate testing_build
Whenever i need to generate a build for current release (with the previous LTS NodeJS)
nvm use currently_used_LTS
clear the node modules
npm install (Release npm-shrinkwrap.json)
generate release_build
Thanks
In theory that should work.
However have you considered the option of just doing a point release for the current release_build that does nothing except version-bump node?
You may find (after re-running your tests) that the latest version of node is backwards compatable with release_build (or only requires minor fixes), and you can simplify your life by porting everything to the latest node version, rather than constantly switching
I'm doing the developers tutorial found here: https://hyperledger.github.io/composer/v0.16/tutorials/developer-tutorial.html
On the step where you have to runtime install I call this command:
composer runtime install --card PeerAdmin#hlfv1 --businessNetworkName tutorial-network
But get the following error:
Unknown arguments: card, businessNetworkName, runtime, install
Ive looked through the composer-cli documentation and runtime is still in there. Is the documentation out-dated or what else might be going wrong here. I'm absolutly clueless.
You are looking at a tutorial for the version v0.16 - this is now quite dated and unless you are specifically using this version you should use the latest doc and the latest Composer version.
The latest doc is here: https://hyperledger.github.io/composer/latest/tutorials/developer-tutorial
Check you version of Composer with composer -v hopefully you are using v0.19.6 or similar.
(Composer runtime install was a v0.16 command and no longer present in v0.19.* - the new commands are in the tutorial.)
Composer v0.19.* works with Fabric v1.1.0 - this is the latest version and hopefully this is the version you have. You can check your Fabric version by using docker images and you should see image names ending -1.1.0 If not you will need to remove the existing containers and images and re-do the step to create the Development Fabric as described in the latest docs.
When I generate a microservice project the consule docker-compose file suggests version 0.9.7 of the docker docker image.
Would it be ok to use the most recent version which is version 1.0.7, or is there a specific reason for version 0.9.3 ?