-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
peer lifecycle chaincode install fails with podman #4606
Comments
@rlfnb
From the above description, it seems that since Podman does not have a Docker-Daemon, it is necessary to use External Chaincode as a Service. |
sorry for late reply. @satota2 I think, fabric should deprecate the way to deploy chain codes the "old way" relying on docker, because basically no one will use docker to run fabric today and its fully incompatible to run HLF in kubernetes (no docker damon at all). What do you think? |
@rlfnb I would also like to see Fabric deprecate the old built in chaincode support, although I think there needs to be better out of the box support for the new(ish!) builder and launcher framework first. Currently the only built in builder/launcher is the chaincode as a server builder, which is great for developing and debugging chaincode but is fiddly to get working and is not well suited to production deployments. There's also issue #3649 to add an out of the box "binary" builder, which could help with the initial Fabric experience, test networks, etc. but needs a bit more thought... and implementing! And finally, there's the Kubernetes builder lab project which I hope will provide a better option for production deployments on Kubernetes. |
Description
Packaged a chain contract and tried to install it with the following command:
peer lifecycle chaincode install mycc.tar.gz
I'm using on my machine podman instead of docker and basically all the remaining things work like a charm. Is there an existing env variable I can use to make it work with podman?
Steps to reproduce
The text was updated successfully, but these errors were encountered: