Tools, FAQ, Tutorials:
"fabric-nodeenv:latest not found" Error
How to resolve the "hyperledger/fabric-nodeenv:latest not found" error?
Based on discussions on the Internet, there is a something wrong in the Docker image repository for "hyperledger/fabric-nodeenv:latest" image.
When you try to instantiate chaincode a Hyplerledger Fabric network channel, a docker container needs to be created from a specific version of hyperledger/fabric-nodeenv image. If your Hyplerledger Fabric network channel is configured to use the "latest" version, you will get the following error:
Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-nodeenv:latest: API error (404): manifest for hyperledger/fabric-nodeenv:latest not found
One way to avoid the problem is to configure the Hyplerledger Fabric network to use specific version of Docker images.
1. Modify ../basic-net/docker-compose.yml to use amd64-1.4.0 image version for all containers, except for couchdb:
$ cd ~/hyperledger-binaries/fabric-samples/fabcar $ vi ../basic-net/docker-compose.yml # Copyright IBM Corp All Rights Reserved version: '2' networks: basic: services: ca.example.com: container_name: ca.example.com image: hyperledger/fabric-ca:amd64-1.4.0 ... orderer.example.com: container_name: orderer.example.com image: hyperledger/fabric-orderer:amd64-1.4.0 ... peer0.org1.example.com: container_name: peer0.org1.example.com image: hyperledger/fabric-peer:amd64-1.4.0 ... couchdb: container_name: couchdb image: hyperledger/fabric-couchdb ... cli: container_name: cli image: hyperledger/fabric-tools:amd64-1.4.0 ...
2. Remove all container images manually, since ./teardown.sh is not working:
$ docker rmi hyperledger/fabric-ca:latest $ docker rmi hyperledger/fabric-orderer:latest $ docker rmi hyperledger/fabric-peer:latest $ docker rmi hyperledger/fabric-couchdb:latest $ docker rmi hyperledger/fabric-tools:latest
3. Re-run ./startFabric.sh to download, deploy and start it again:
As you can see, the "hyperledger/fabric-nodeenv:latest not found" error is not showing up anymore.
â‡’ fabcar.go - The "fabcar" Chaincode
â‡ Reinstall Chaincode on WYFA Network
â‡‘ WYFA (Writing Your First Application)
â‡‘â‡‘ Hyperledger Tutorials
2020-02-29, 1243👍, 0💬
How to View Atom Feeds with IE (Internet Explorer)? If you want to view Atom Feeds with IE (Internet...
How to use the API operation 2017 version setting "Rewrite URL template"? The API operation setting ...
How to send an FTP request with the urllib.request.urlopen() function? If an FTP server supports ano...
Where to see resource detailed information of my API Management Service on Azure Portal? Once you ha...
How to use "xsl-transform" Azure API Policy Statement? The "xsl-transform" Policy Statement allows y...