DBIS Hyperledger Runtime Status

Last Reviewed: 2026-03-28
Purpose: Concise app-level status table for the non-Besu Hyperledger footprint currently hosted on Proxmox. This complements the VMID inventory and discovery runbooks by recording what was actually verified inside the running containers.

Scope

This document summarizes the latest operator verification for:

FireFly CTs: 6200, 6201
Fabric CTs: 6000, 6001, 6002
Indy CTs: 6400, 6401, 6402

The checks were based on:

pct status
in-container process checks
in-container listener checks
FireFly API / Postgres / IPFS checks where applicable

Current status table

VMID	Service family	CT status	App-level status	Listening ports / probe	Notes
`6200`	FireFly primary	Running	Healthy minimal local gateway	`5000/tcp` FireFly API, `5432/tcp` Postgres, `5001/tcp` IPFS	`firefly-core` restored on `ghcr.io/hyperledger/firefly:v1.2.0`; `GET /api/v1/status` returned `200`; Postgres `pg_isready` passed; IPFS version probe passed
`6201`	FireFly secondary	Stopped	Standby / incomplete	None verified	CT exists but rootfs is effectively empty and no valid FireFly deployment footprint was found; do not treat as active secondary
`6000`	Fabric primary	Running	Unproven	No Fabric listener verified	CT runs, but current app-level checks did not show active peer/orderer processes or expected listeners such as `7050` / `7051`
`6001`	Fabric secondary	Running	Unproven	No Fabric listener verified	Same current state as `6000`
`6002`	Fabric tertiary	Running	Unproven	No Fabric listener verified	Same current state as `6000`
`6400`	Indy primary	Running	Unproven	No Indy listener verified	CT runs, but current checks did not show Indy node listeners on expected ports such as `9701`-`9708`
`6401`	Indy secondary	Running	Unproven	No Indy listener verified	Same current state as `6400`
`6402`	Indy tertiary	Running	Unproven	No Indy listener verified	Same current state as `6400`

Interpretation

Confirmed working now

FireFly primary (6200) is restored enough to provide a working local FireFly API backed by Postgres and IPFS.

Present but not currently proved as active application workloads

Fabric CTs (6000-6002)
Indy CTs (6400-6402)

These should be described as container footprints under validation, not as fully verified production application nodes, until app-level services and expected listeners are confirmed.

Not currently active

FireFly secondary (6201) should be treated as standby or incomplete deployment state unless it is intentionally rebuilt and verified.

Operational follow-up

Keep 6200 under observation and preserve its working config/image path.
Do not force 6201 online unless its intended role and deployment assets are re-established.
For Fabric and Indy, the next verification step is app-native validation, not more CT-level checks.
Any governance or architecture document should distinguish:
- deployed and app-healthy
- container present only
- planned / aspirational

3.6 KiB Raw Blame History