Contribute in GitHub:
Open doc issue|Edit online
Upgrading IBM Support for Hyperledger Fabric
There are two types of upgrades when updating IBM Support for Hyperledger Fabric. Fix pack upgrades are performed for updating minor changes and for making new Fabric versions available in the console. Upgrades are used when a new release version is issued. A new release is issued when major changes are made to underlying components or changes are made that may require Fabric component (peers, orderers, CAs) restarts.
If you are behind a firewall or using a local repository, you must pull the IBM Support for Hyperledger Fabric images before beginning the upgrade or fix pack process.
The following table shows the listing of releases and fix packs.
| Release | Type | Release Date | Instructions |
|---|---|---|---|
| 1.0.9-20251112 | fix pack | November 12, 2025 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20250922 | fix pack | September 19, 2025 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20250722 | fix pack | July 22, 2025 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20250506 | fix pack | May 06, 2025 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20250325 | fix pack | March 25, 2025 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20250218 | fix pack | February 18, 2025 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20241210 | fix pack | December 10, 2024 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20241008 | fix pack | October 08, 2024 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20240903 | fix pack | September 03, 2024 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20240806 | fix pack | August 06, 2024 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20240702 | fix pack | July 02, 2024 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20240604 | fix pack | June 04, 2024 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20240507 | fix pack | May 07, 2024 | Apply Fix Pack (If you have not upgraded to version 1.0.9 yet, perform the 1.0.9 upgrade first.) |
| 1.0.9-20240402 | upgrade | April 02, 2024 | 1.0.9 Upgrade |
| 1.0.8-20240305 | fix pack | March 05, 2024 | Apply Fix Pack (If you have not upgraded to version 1.0.8 yet, perform the 1.0.8 upgrade first.) |
| 1.0.8-20240206 | fix pack | February 06, 2024 | Apply Fix Pack (If you have not upgraded to version 1.0.8 yet, perform the 1.0.8 upgrade first.) |
| 1.0.8-20240111 | fix pack | January 11, 2024 | Apply Fix Pack (If you have not upgraded to version 1.0.8 yet, perform the 1.0.8 upgrade first.) |
| 1.0.8-20231212 | upgrade | December 12, 2023 | 1.0.8 Upgrade |
| 1.0.7-20231114 | upgrade | November 14, 2023 | 1.0.7 Upgrade |
| 1.0.6-20231010 | fix pack | October 10, 2023 | Apply Fix Pack (If you have not upgraded to version 1.0.6 yet, perform the 1.0.6 upgrade first.) |
| 1.0.6-20230905 | upgrade | September 7, 2023 | 1.0.6 Upgrade |
| 1.0.5-20230808 | fix pack | August 8, 2023 | Apply Fix Pack |
| 1.0.5-20230711 | fix pack | July 13, 2023 | Apply Fix Pack |
NOTE: Previous fix packs other than the current can be installed by changing the image tags of the webhook and operator images in the fix pack instructions to match the release in the above table. Remember that Fabric components can not be reverted once they are upgraded.
Pull the IBM Support for Hyperledger Fabric images
You can download the complete set of IBM Support for Hyperledger Fabric images from the cpopen registry. To deploy the platform without access to the public internet, you need to pull the images and then push the images to a container registry that you can access from behind your firewall.
It is recommended to use the skopeo utility to download and copy your images to your local container registry. The skopeo tool is used for moving container
images between different types of container storages. In order to download the platform images and copy them to your container registry behind a firewall, you first need to install skopeo.
The following commands only work with a Docker container registry. Depending on the level of permissions required for the target location for the images, you might need to prefix each command with sudo.
The platform recommends that you use the skopeo utility to download and copy your images to your local container registry. skopeo is a tool for moving container
images between different types of container storages. In order to download the platform images and copy them to your container registry behind a firewall, you first need to install skopeo.
Run the following set of commands to download the images and push them to your registry.
Replace:
<LOCAL_REGISTRY_USER>with the user ID with access to your container registry.<LOCAL_REGISTRY_PASSWORD>with the password to your container registry.
The following commands only work with a Docker container registry. Depending on the level of permissions required for the target location for the images, you might need to prefix each command with sudo.
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport-operator:1.0.9-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-operator:1.0.9-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport-crdwebhook:1.0.9-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-crdwebhook:1.0.9-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-console:1.0.9-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-console:1.0.9-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-deployer:1.0.9-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-deployer:1.0.9-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport-mustgather:1.0.9-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-mustgather:1.0.9-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-init:1.0.9-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-init:1.0.9-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-enroller:1.0.9-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-enroller:1.0.9-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-couchdb:3.3.3-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-couchdb:3.3.3-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-ca:1.5.15-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-ca:1.5.15-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-grpcweb:1.0.9-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-grpcweb:1.0.9-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-orderer:2.5.12-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-orderer:2.5.12-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-utilities:2.5.12-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-utilities:2.5.12-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-peer:2.5.12-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-peer:2.5.12-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-chaincode-launcher:2.5.12-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-chaincode-launcher:2.5.12-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-ccenv:2.5.12-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-ccenv:2.5.12-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-goenv:2.5.12-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-goenv:2.5.12-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-nodeenv:2.5.12-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-nodeenv:2.5.12-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all
skopeo copy docker://icr.io/cpopen/ibm-hlfsupport/ibm-hlfsupport-javaenv:2.5.12-20251112-amd64 <LOCAL_REGISTRY>/ibm-hlfsupport-javaenv:2.5.12-20251112-amd64 -q --dest-creds <LOCAL_REGISTRY_USER>:<LOCAL_REGISTRY_PASSWORD> --all