How to use this image

All examples in this guide use the public image. If you’ve mirrored the repository for your own use (for example, to your Docker Hub namespace), update your commands to reference the mirrored image instead of the public one.

For example:

• Public image: dhi.io/<repository>:<tag>
• Mirrored image: <your-namespace>/dhi-<repository>:<tag>

For the examples, you must first use docker login dhi.io to authenticate to the registry to pull the images.

What's included in this Hyperledger Fabric Orderer Hardened image

The Hyperledger Fabric Orderer service provides an atomic broadcast ordering service for consumption by the peers in a Hyperledger Fabric blockchain network. This means that many clients can submit messages to the ordering service, and the same sequence of ordered batches will be delivered to all clients in response. The hardened image provides the same functionality as upstream Hyperledger Fabric but runs with Docker Hardened Image security guarantees.

Using Hyperledger Fabric Orderer

Run commands using docker run with Hyperledger Fabric Orderer. Replace <tag> with the desired version. Files provided in the example can be generated using teh cryptogen tool or fabric-ca.

docker run -d --publish 7050:7050 \
-v /tmp/fabric/config/orderer.example.com:/etc/hyperledger/fabric \
-v /tmp/fabric/config/ordererOrganizations/example.com/orderers/orderer.example.com/msp:/etc/hyperledger/fabric/msp \
-v /tmp/fabric/config/ordererOrganizations/example.com/orderers/orderer.example.com/tls:/etc/hyperledger/fabric/tls \
-v /tmp/fabric/data/orderer.example.com:/var/hyperledger/production \
--name orderer.example.com dhi.io/hyperledger-fabric-orderer:<tag>

Common Hyperledger Fabric Orderer use cases

The https://github.com/hyperledger/fabric-samples⁠ repository includes samples that can be used to create Hyperledger Fabric networks. The test-network directory, for example includes materials and a script, network.sh that can be used to create a test network with docker-compose. To deploy a network using the hardened image, simply replace the image in the docker compose file, for the test-network example located at test-network/compose/compose-test-net.yaml, from hyperledger/fabric-orderer:latest to dhi.io/hyperledger-fabric-orderer:<tag>.

See documentation at https://hyperledger-fabric.readthedocs.io/⁠ and https://github.com/hyperledger/fabric-samples⁠ for further details on running Hyperledger Fabric and the provided examples.

Non-hardened images vs Docker Hardened Images

Key differences

Hardened image debugging

Docker Hardened Images for Hyperledger Fabric Orderer do not include a shell or package manager to minimize the attack surface and reduce image size. This means you cannot use docker exec to access a shell inside a running container. However, Docker provides alternative debugging methods that work seamlessly with hardened images.

The recommended approach is to use Docker Debug⁠, which attaches an ephemeral debug container with a shell and common debugging tools to your running container. This allows you to inspect the container's filesystem, processes, and network configuration without modifying the production image.

For Hyperledger Fabric Orderer specifically, you can also debug by examining the output artifacts (genesis blocks, configuration files, certificates) generated by the tools. Mount volumes to persist these outputs and inspect them on your host system. Additionally, enable verbose logging by checking tool-specific flags (many tools support -v or --verbose flags).

Using Docker Debug

Attach a debug shell to a running Hyperledger Fabric Orderer container:

docker debug <container-name>

This opens a shell in the debug container where you can inspect the filesystem, check running processes with ps, or examine network connections with netstat.

Using Docker Image Mount

Mount the container's filesystem to your host for inspection:

docker image mount dhi.io/hyperledger-fabric-orderer:<tag> /mnt/inspect
ls -la /mnt/inspect/usr/local/bin/

Image variants

Docker Hardened Images come in different variants depending on their intended use.

• Runtime variants are designed to run your application in production. These images are intended to be used either directly or as the FROM image in the final stage of a multi-stage build. These images typically:

  • Run as the nonroot user
  • Do not include a shell or a package manager
  • Contain only the minimal set of libraries needed to run the app

• Build-time variants typically include dev in the variant name and are intended for use in the first stage of a multi-stage Dockerfile. These images typically:

  • Run as the root user
  • Include a shell and package manager
  • Are used to build or compile applications

Migrate to a Docker Hardened Image

To migrate your application to a Docker Hardened Image, you must update your Dockerfile. At minimum, you must update the base image in your existing Dockerfile to a Docker Hardened Image. This and a few other common changes are listed in the following table of migration notes.

The following steps outline the general migration process.

1. Find hardened images for your app.

   A hardened image may have several variants. Inspect the image tags and find the image variant that meets your needs.

2. Update the base image in your Dockerfile.

   Update the base image in your application's Dockerfile to the hardened image you found in the previous step. For framework images, this is typically going to be an image tagged as dev because it has the tools needed to install packages and dependencies.

3. For multi-stage Dockerfiles, update the runtime image in your Dockerfile.

   To ensure that your final image is as minimal as possible, you should use a multi-stage build. All stages in your Dockerfile should use a hardened image. While intermediary stages will typically use images tagged as dev, your final runtime stage should use a non-dev image variant.

4. Install additional packages

   Docker Hardened Images contain minimal packages in order to reduce the potential attack surface. You may need to install additional packages in your Dockerfile. Inspect the image variants to identify which packages are already installed.

   Only images tagged as dev typically have package managers. You should use a multi-stage Dockerfile to install the packages. Install the packages in the build stage that uses a dev image. Then, if needed, copy any necessary artifacts to the runtime stage that uses a non-dev image.

   For Alpine-based images, you can use apk to install packages. For Debian-based images, you can use apt-get to install packages.

Troubleshooting migration

The following are common issues that you may encounter during migration.

General debugging

The hardened images intended for runtime don't contain a shell nor any tools for debugging. The recommended method for debugging applications built with Docker Hardened Images is to use Docker Debug⁠ to attach to these containers. Docker Debug provides a shell, common debugging tools, and lets you install other tools in an ephemeral, writable layer that only exists during the debugging session.

Permissions

By default image variants intended for runtime, run as the nonroot user. Ensure that necessary files and directories are accessible to the nonroot user. You may need to copy files to different directories or change permissions so your application running as the nonroot user can access them.

Privileged ports

No shell

By default, image variants intended for runtime don't contain a shell. Use dev images in build stages to run shell commands and then copy any necessary artifacts into the runtime stage. In addition, use Docker Debug to debug containers with no shell.

Entry point

Docker Hardened Images may have different entry points than images such as Docker Official Images. Use docker inspect to inspect entry points for Docker Hardened Images and update your Dockerfile if necessary.