Skip to content
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

Closed
kirbyclements opened this issue Oct 1, 2020 · 12 comments
Closed

deployCC: docker build failed: docker image inspection failed #4955

kirbyclements opened this issue Oct 1, 2020 · 12 comments

Comments

@kirbyclements
Copy link

  • [ x ] I have tried with the latest version of my channel (Stable or Edge)
  • [ x ] I have uploaded Diagnostics
  • Diagnostics ID: 4C67AC08-5CC5-4055-A502-273269890D49/20201001122820

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:

Information

  • macOS Version: Big Sur

Diagnostic logs

Docker for Mac: version...
2.3.7.0

Steps to reproduce the behavior

  1. ... The hyperledger command being used is 'deployCC' where the chaincode is built.
  2. ... This spurs the error when connecting to the socket in /var/run on the mac os
@kirbyclements
Copy link
Author

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.

@djs55
Copy link
Contributor

djs55 commented Oct 1, 2020

@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 docker build available somewhere?

@TschonnyCache
Copy link

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?

@nzupan
Copy link

nzupan commented Oct 26, 2020

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.

@eesati
Copy link

eesati commented Nov 8, 2020

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.
Many thanks to you.

@palles77
Copy link

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/

@nileshpanhale1601
Copy link

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.

@markpengisme
Copy link

@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/

@nileshpanhale1601
Copy link

nileshpanhale1601 commented Dec 30, 2020 via email

@juliofeng
Copy link

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.

Exactly the same!

@docker-robott
Copy link
Collaborator

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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.
/lifecycle stale

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

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.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Aug 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants