我试图使用以下命令查询事务并看到以下错误
peer chaincode query -n <chaincodeId> -c '{"Function": "query", "Args": ["a"]}' -u jim
23:52:59.542 [crypto] main -> INFO 001 Log level recognized 'info', set to INFO
Usage:
peer chaincode query [flags]
Flags:
-x, --hex[=false]: If true, output the query value byte array in hexadecimal. Incompatible with --raw
-r, --raw[=false]: If true, output the query value as raw bytes, otherwise format as a printable string
Global Flags:
-c, --ctor="{}": Constructor message for the chaincode in JSON format
-l, --lang="golang": Language the chaincode is written in
--logging-level="": Default logging level and overrides, see core.yaml for full syntax
-n, --name="": Name of the chaincode returned by the deploy transaction
-p, --path="": Path to chaincode
-u, --username="": Username for chaincode operations when security is enabled
错误：查询链代码时出错：rpc 错误：代码 = 2 desc =“错误：无法启动链代码规范（启动容器时出错：无法连接到 Docker 端点）”
我在 NON-DEV 模式下运行 peer（模式：net）。在网络模式下，验证器将在 docker 容器中运行链代码。
对等节点日志小结
23:14:57.568 [devops] invokeOrQuery -> DEBU 03c 使用上下文 jim 初始化安全 devops 23:14:57.568 [crypto] invokeOrQuery -> INFO 03d 初始化客户端 [jim]... 23:14:57.682 [crypto] invokeOrQuery - > INFO 03e 正在初始化客户端 [jim]...完成！23:14:57.682 [devops] createExecTx -> DEBU 03f 创建安全调用事务 774fd330-ed1f-4a4d-b472-15386f3b5505 23:14:57.683 [devops] invokeOrQuery -> DEBU 040 发送调用事务 (774fd330-ed1f-4a2d-b47 -15386f3b5505) 到验证器 23:14:57.683 [peer] sendTransactionsToLocalEngine -> DEBU 041 编组事务 CHAINCODE_QUERY 发送到本地引擎 23:14:57.683 [peer] sendTransactionsToLocalEngine -> DEBU 042 发送消息 CHAIN_TRANSACTION 时间戳秒：1463786097 纳秒：6836到本地引擎 23:14:57.950 [chaincode] getArgsAndEnv ->start container : 7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568(networkid:dev,peerid:vp0) 23:14:57.950 [container] lockContainer -> DEBU 045 waiting for container (dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568) lock 23:14:57.950 [container] lockContainer -> DEBU 046 got container (dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568) lock 23:14:57.950 [dockercontroller] Start -> DEBU 047 Cleanup containerdev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568 23:14:57.950 [dockercontroller] stopInternal -> DEBU 048 Stop container dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568( cannot connect to Docker endpoint ) 23:14:57.950 [dockercontroller] stopInternal -> DEBU 049 Kill container dev-vp0 -7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568 ( cannot connect to Docker endpoint ) 23:14:57.951 [dockercontroller] stopInternal -> DEBU 04a Remove containerdev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568 (cannot connect to Docker endpoint) 23:14:57.951 [dockercontroller] Start -> DEBU 04b Start container dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568 23:14:57.951 [dockercontroller] createContainer -> DEBU 04c Create container : dev- vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568 23:14:57.951 [dockercontroller] Start -> ERRO 04d start-could not recreate container cannot connect to Docker endpoint 23:14:57.951 [container] unlockContainer -> DEBU 04econtainer lock deleted (dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568) 23:14:57.951 [chaincode] LaunchChaincode -> DEBU 04f launchAndWaitForRegister failed Error starting container: cannot connect to Docker endpoint 23:14:57.951 [crypto] CloseClient -> INFO 050 Closing client [吉姆]...
这里的问题是为什么容器被脱机又名终止？