<p>I am creating a hyperledger fabric network using the following hyperledger fabric operator for kubernetes <a href="https://github.com/hyperledger-labs/hlf-operator" rel="nofollow noreferrer">https://github.com/hyperledger-labs/hlf-operator</a> I have my cluster configured in aws eks and it is currently running 3 nodes. I am following the documentation and so far all the steps of the implementation are working without problem, but when installing my chaincode it shows me the following message:</p>
<pre><code>'InstallChaincode': could not build chaincode: docker build failed: docker build is disabled
</code></pre>
<p>Validate and change docker permissions but I don't understand what I am missing so that it can work and install my chaincode.</p>
<p>I think it may be a permissions error in the eks, I am also validating the permissions</p>

<p>I encountered the same problem and I finally solved it. The problem is when you create your peer node right now (as of July 28, 2022), the version defaults to <code>2.3.0-v0.0.2</code> (you can find this <code> kubectl hlf peer create --help</code> and see the description next to the <code>--version</code> flag). This peer version happens to be incompatible when deploying <code>ccaas</code> - chaincode as a service. So, the solution is to manually override the version using the <code>--version</code> flag while creating the peer node. Peer version <code>2.4.1-v0.0.4</code> solved this for me.</p>
<p>Please see the below command while creating a <code>peer</code> node for <code>org1</code>.</p>
<pre><code>kubectl hlf peer create --statedb=couchdb --storage-class=standard --enroll-id=org1-peer --mspid=Org1MSP --enroll-pw=peerpw --capacity=5Gi --name=org1-peer0 --ca-name=org1-ca.fabric --version=2.4.1-v0.0.4 --namespace=fabric
</code></pre>
<p>Note the above steps apply only when you are using the peer image from <code>quay.io/kfsoftware/fabric-peer</code> which is the default image. If you want to use other images use the <code>--image</code> tag.  Repeat the same steps while creating every peer node. This should solve your problem. Hope this helps!</p>
