小编Chi*_*vir的帖子

我正在尝试使用 Fabric Node SDK 在我的 Hyperledger Fabric 网络（在云上设置）上实例化 Golang 链代码。但是，我在执行相同操作时遇到以下错误：

Error: error starting container: error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-ccenv:latest: API error (404): manifest for hyperledger/fabric-ccenv:latest not found: manifest unknown: manifest unknown

相同的堆栈跟踪是：

at self._endorserClient.processProposal (./node_modules/fabric-client/lib/Peer.js:140:36)
at Object.onReceiveStatus (./node_modules/grpc/src/client_interceptors.js:1207:9)
at InterceptingListener._callNext (./node_modules/grpc/src/client_interceptors.js:568:42)
at InterceptingListener.onReceiveStatus (./node_modules/grpc/src/client_interceptors.js:618:8)
at callback (./node_modules/grpc/src/client_interceptors.js:845:24)

我还尝试hyperledger/fabric-ccenv在本地环境中直接拉取图像，但在那里也遇到了类似的错误：

命令：

docker pull hyperledger/fabric-ccenv

错误：

Using default tag: latest
Error response from daemon: manifest for hyperledger/fabric-ccenv:latest not found: manifest unknown: manifest unknown …

我正在尝试在我的 Windows 10 机器上运行 Hadoop 3.1.1。我修改了所有文件：

• hdfs-site.xml
• mapred-site.xml
• 核心站点.xml
• 纱线站点.xml

然后，我执行了以下命令：

C:\hadoop-3.1.1\bin> hdfs namenode -format

格式运行正确，因此我指示C:\hadoop-3.1.1\sbin执行以下命令：

C:\hadoop-3.1.1\sbin> start-dfs.cmd

命令提示符会打开 2 个新窗口：一个用于 datanode，另一个用于 namenode。

namenode 窗口继续运行：

2018-09-02 21:37:06,232 INFO ipc.Server: IPC Server Responder: starting
2018-09-02 21:37:06,232 INFO ipc.Server: IPC Server listener on 9000: starting
2018-09-02 21:37:06,247 INFO namenode.NameNode: NameNode RPC up at: localhost/127.0.0.1:9000
2018-09-02 21:37:06,247 INFO namenode.FSNamesystem: Starting services required for active state
2018-09-02 21:37:06,247 INFO namenode.FSDirectory: Initializing quota with 4 thread(s)
2018-09-02 21:37:06,247 INFO namenode.FSDirectory: Quota initialization completed …

我正在尝试在configtx.yaml文件内的策略定义中添加自定义节点 OU 。策略定义位于 configtx.yaml 文件的应用程序部分，如下所示：

Application: &ApplicationDefaults

# Organizations is the list of orgs which are defined as participants on
# the application side of the network
ACLs: &ACLsDefault
    peer/Propose: /Channel/Application/Checkous

Organizations:

# Policies defines the set of policies at this level of the config tree
# For Application policies, their canonical path is
#   /Channel/Application/<PolicyName>
Policies:
    Readers:
        Type: ImplicitMeta
        Rule: "ANY Readers"
    Writers:
        Type: ImplicitMeta
        Rule: "ANY Writers"
    Admins:
        Type: ImplicitMeta
        Rule: "MAJORITY Admins"
    Checkous:
        Type: Signature
        Rule: …