1. The fabric version used is v2.2.4. Test the test network
2. Problem description
When calling the basic chain code, the following error messages are found:
error: Endorsement failure during invoke. Response: status: 500 message: “error in simulation: failed to execute transaction 75a77550b68a7476882e7a512fa0dd4f0accd90e9f1db7e5193c914dd91bb285: could not launch chaincode basic_ 1.0:3cfcf67978d6b3f7c5e0375660c995b21db19c4330946079afc3925ad7306881: error starting container: error starting container: API error (404): network fabric_ test not found”
This fabric_test has different results according to different versions.
the essence is that the name of the started fabric network is wrong, which is inconsistent with the configuration in our. Yaml file and the docker compose
3. The solution is as follows:
Premise: after I have finished the./network up createChannel and the chain code, the chain code will come up. Do not do the following instructions directly after down!!!!!
3.1 first, we execute the following commands:
docker network ls
The display result is
3.2 open the test network/docker/docker-compose-test-net.yaml file
see
you can find that the name here is incorrect and you need to modify it to the docker displayed by docker network ls_ test。
note that in this file
CORE_ VM_ DOCKER_ HOSTCONFIG_ NETWORKMODE=fabric_ Test
there are two places, so we need to change two places.
After modification, it can be called successfully.
Read More:
- Docker creation container cannot find network card: error response from daemon: network XXXX not found
- Error running docker container: starting container process caused “exec: \“python\“: executable file
- [Solved] kubelet Startup Error: cannot find network namespace for the terminated container
- Solve the problem of springboot and unit test starting applicationrunner
- Problem: error (24) file not found is prompted when importing the network table
- An error occurred when starting Tomcat in Eclipse: the sub container failed to start
- A new virtual machine cannot be connected to the network (error fetching interface information device not found),
- Debian using networking to restart the network can not start the solution of network card
- Error: path not specified when the docker 1.7 file is uploaded to the container in CentOS
- NACOS error com.alibaba.nacos.api.exception.NacosException: failed to req API:/api//nacos/v1/ns/instance
- Error starting day: SELinux is not supported with the overlay 2
- import org.junit.Test And @ test error reporting — solutions
- Python normality test: test whether the data obey the normal distribution
- [Solved] com.alibaba.nacos.api.exception.NacosException: failed to req API
- Get connection timeout retry: 1 MySQL errorcode 0, state 08s01 docker container accessing MySQL container is very slow and sometimes interrupted
- Wireless network solution of deepin Linux network card driver (manual) installation
- Fabric appears when trying to use application call: Unknown: access denied: Channel [mychannel] creator org [org1msp]
- [solved] – bash: rabbitmq plugins: command not found or RA bbitmqctl:command not found
- Linux virtual machine network “job for” network.service failed because the control process exited with error code”
- docker.errors.DockerException: Error while fetching server API version: (‘Connection aborted.‘, File