-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deployCC: docker build failed: docker image inspection failed #4955
Comments
Got it working again! I turned off Kubernetes (though I think it will work again with Kubernetes and will turn it on shortly - know there are plenty of working versions with that obviously). I also unchecked the box in Docker Desktop for Mac OS for 'Use gRPC FUSE for file sharing - Switch off to use the legacy osxfs file sharing instead.’ I think this preference for gRPC FUSE was the issue, but will determine if it’s both changes that did the trick or just one or other. |
@kirbyclements thanks for your report! Let us know what more you find out. Once you've narrowed it down as much as you can, could you provide some repro instructions? Is the source code for |
I'm on mac os mojave and have the same error. kirbyclements's fix (turning of kubernetes and gRPC) does not do the job for me eiter. Any other ideas? |
I had the same problem on my Mac after updating docker (Docker version 19.03.13, build 4484c46d9d). Disabling "Use gRPC FUSE for file sharing" in the docker settings solved my issue. |
You are amazing my man, this was my first installation of hyperledger and you saved me. |
I had similar issue. It was resolved by reinstalling docker to newest version 19.03.13. I followed instructions from https://docs.docker.com/engine/install/ubuntu/ |
facing the same issue. after updating docker to v20.10.0 and switching off gRPC FUSE for file sharing, had error on channel creation. if I switch on gRPC FUSE for file sharing, then had this chaincode error. can't understand what to do... this is my first network setup on macos bigsur... Please help asap. |
@nileshpanhale1601 |
Hello Mark,
Thank you so much for the solution. Today I tried with Docker version 18
(2.0.0.3). Now I can run all commands of the test network successfully.
Thank you. Regards.
…On Wed, Dec 30, 2020 at 1:02 PM Mark Peng ***@***.***> wrote:
@nileshpanhale1601 <https://github.com/nileshpanhale1601>
I faced the same issue, but I try to reinstall another version ( Docker
Desktop Community 2.5.0.1), and it can work the tutorial "using the Fabric
test network" in Hyperledger fabric docs, just for your reference.
https://docs.docker.com/docker-for-mac/release-notes/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4955 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AL2IGDIMZO45IEIFQT2NUFLSXLJRLANCNFSM4SAMCHUQ>
.
|
Exactly the same! |
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
deploy the chaincode as was done earlier in day yesterday, prior to new stable update to Docker Stable version, latest
Actual behavior
fails here:
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/dev-peer0.org1.example.com-basic_1.0-4ec191e793b27e953ff2ede5a8bcc63152cecb1e4c3f301a26e22692c61967ad-42f57faac8360472e47cbbbf3940e81bba83439702d085878d148089a1b213ca/json": dial unix /host/var/run/docker.sock: connect: no such file or directory
Information
Diagnostic logs
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: