hyperledger
Upgrading the fabric components
Type of change
- Improvement (improvement to code, performance, etc)
Description
I was trying to upgrade the chaincode version from v2.2 to v2.5.4 so I went to the documentation and tried to do the steps mentioned in the documentation. When I tried with those commands I faced different errors. The errors I encountered are couldn't run the orderer container as the orderer was looking for certificates which was not backed up. The opt path in the docker container has no files in it. Instead we have to backup from var directory which includes both the orderer and production folders. In the peer container we have to mention the name of the fabric network for the chaincode container to start otherwise the chaincode container is not starting. So I fixed all the errors and made a new documentation for upgrading the fabric components and upgrading the capabilities.
Additional details
Added upgrading steps for couchdb and fabric-ca also.
Related issues
https://github.com/hyperledger/fabric/issues/4862
@Vishva066, Thanks for your contribution. Could you please sign off on your commitment to making DCO checks happy?
@Vishva066 I'm following up on this pull request for upgrading Fabric components documentation.
It's been almost a year since this PR was opened, and there hasn't been any activity since May 2024. As mentioned, the commits need to be signed off to pass the DCO checks before this can be merged.
Given the lack of recent activity, we're considering closing this PR. If you're still interested in contributing this documentation improvement, please let us know and address the DCO signing requirement.
If we don't hear back soon, we'll close this PR for housekeeping. You're always welcome to reopen it or create a new PR when you have time to complete the submission and address the comments.