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 ?
Related
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.
CycloneDX for NPM states that it requires Node version 12. If I have an older project (for example an Angular 7 project) that only supports Node version 10. Can I run CycloneDX for NPM on the commandline as a docker container to generate an SBOM? Or must the project also support Node v12?
I have run the command against an older project and it seems to work, however I'm concerned that the generated SBOM might be incomplete or inaccurate due to the Node version. Updating the application to a newer version of Angular is possible as a long-term solution, however
short-term I was wondering simply running the app in a container will work.
I am getting an error while deploying my site
Minimum Node version not met :(
You are using Node v12.22.2. We require Node >=14 or up!
tried updating buildspec.yaml file with node update commands npm install -g node,
Try running n 14.18.3.
The n package is pre-installed on (at least some) CodeBuild runtimes which you can use to install another version and select among installed versions.
Details here.
The default AWS linux container used by CodeBuild only supports nodejs version 12.x, so change it to the ubuntu image aws/codebuild/standard:5.0 that supports node version 14.x
See AWS Available Runtimes for nodejs
Initially, i faced the issue, that concurrency doesn't work in Jenkins. I find this issue in official repository and followed advise to update Testcafe Docker Image to latest version (i took it from testcafe/testcafe repository). However, now i faced another issue. We have node-sass package using for web app which i test, and node-sass doesn't work with Node 10.x and displays this error message
Module build failed: Error: Missing binding /tests/node_modules/node-sass/vendor/linux_musl-x64-64/binding.node
Node Sass could not find a binding for your current environment: Linux/musl 64-bit with Node.js 10.x
Found bindings for the following environments:
- Linux/musl 64-bit with Node.js 8.x
This usually happens because your environment has changed since running `npm install`.
Run `npm rebuild node-sass` to download the binding for your current environment.
Is there is some workaround for it, or maybe Testcafe can use Node 8.x and then you can provide Docker Image with this node version?
At the moment we do not have plans to create multiple testcafe docker images for different node versions. However, I created a separate feature request.
Please track that ticket and vote for it. We can add it to our plans in the future.
I am using node 4X ,python 2.7.10 ,java jdk 8.I have installed all dependencies like gcc .
The build error is as below
http://pasted.co/283da73e
Why is the build failing. I had no problem with it on my windows machine.
You're installing an older version of the jdbc module that depends on an older version of the java module that does not support node v4+. Update the jdbc dependency version and it should work.