<p>I am deploying an hyperledger network to an Openshift (Kubernetes) infrastructure. I've already started CA, orderer, and peer0, but using the same yaml configuration that I used to launch peer0 (with obvious changes) to launch peer1, the pod never lauches. Checking peer1 logs I can see the message:</p>

<p><code>panic: Error while trying to open DB: resource temporarily unavailable.</code></p>

<p>Any idea of why could this be happening? There's a related question here <a href="https://stackoverflow.com/questions/47753284/hyperledger-fabric-panic-error-while-trying-to-open-db-resource-temporarily-u">Hyperledger Fabric &quot;panic: Error while trying to open DB: resource temporarily unavailable&quot; during starting a peer</a>, but the suggestion does not apply to my case, because I'm not running the network in a local machine, but in an openshift environment running kubernetes in the background, and peer0 and peer1 are in different pods.</p>

<p>I'm trying to run the peers with LevelDB (default for HLF)</p>

<p>Versions:</p>

<ul>
<li>Hyperledger Fabric 1.1</li>
<li>Openshift 3.5.5.31.66</li>
<li>Kubernetes 1.5.2</li>
</ul>

<p><strong>Update:</strong> Problem solved thanks to Gari Singh comment. Peer1 was using a production volume mount pointing to the same directory as Peer0's.</p>

<p>Thanks</p>

jfc
<p>That error typically occurs when the peer cannot get a lock on DB files.  Make sure that peer0 and peer1 are not mounting the same shared volume.</p>
