Hyperledger Composer模型未持久 [英] Hyperledger Composer model not persisted

问题描述

我在Fabric v1.0上使用Hyperledger Composer.当使用fabric-tools/stopFabric.sh停止Fabric，然后从startFabric.sh开始时，已部署的模型(.bna文件)不再存在.

I'm using Hyperledger Composer on Fabric v1.0. When stopping Fabric with fabric-tools/stopFabric.sh and then starting with startFabric.sh, the deployed model (.bna file) is no longer there.

如何设置系统，以便在系统重新引导后数据保留在其中?

How do I set the system up so that data will stay there after a system reboot?

推荐答案

这是如何设置架构环境的操作注意事项，正如您正确观察到的那样，因为我们的架构开发服务器只是启动架构容器，如果这些容器出于任何原因被破坏，则其内部文件系统将丢失. 在Hyperledger Fabric文档中，他们描述了一种使Fabric容器在其隔离的文件系统之外持久保存其数据的简单方法. 看 http://hyperledger-fabric.readthedocs.io/en/latest/build_network. html 以及有关数据持久性的说明"部分，其中提供了有关此方面的详细信息.在这种情况下，您需要将其中描述的概念应用于我们的Fabric开发服务器中hlfv1/composer目录中的docker-compose.yml文件.

This is an operational consideration for how to set up a fabric environment and as you correctly observe, because our fabric dev server just start up fabric containers, if those containers are destroyed for any reason then their internal filesystem are lost. In the hyperledger fabric documentation they describe a simple way to make the fabric containers persist their data outside of their isolated file systems. see http://hyperledger-fabric.readthedocs.io/en/latest/build_network.html and the section called "A Note on Data Persistence" which provide detail on this. In this case you would need to apply the concepts described there to the docker-compose.yml file in the hlfv1/composer directory in our fabric dev server.

这篇关于Hyperledger Composer模型未持久的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！